Hoover the mouse over the Linked Table and it should show you the ODBC
Connection String of the Linked Table (regardless whether it is linked by
the GUI or VBA code.
Compare the Connection String of a working Table and a faulty Table for
differences, especially the element "Regional=Yes;". If the working one has
Regional element and the faulty one hasn't, then you know what to do.
--
HTH
Van T. Dinh
MVP (Access)
"Lorenz Ingold" <l.ingold[ at ]comteach.ch> wrote in message
news:dmn89b$ncs$6[ at ]news.imp.ch...
[Quoted Text] >I have a very strange special effect (I mean an error situation) on some
> PCs. We have an Access 2003 project (a normal mdb-File, which is to be
> understood as the main application), and as a backend we use SQL-Server
> 2000. The mdb created (with VBA) Links to Tables of SQL-Server, with the
> following code (fragment):
>
> Set tdfNew = dbsDao.CreateTableDef(strLocalName)
> tdfNew.SourceTableName = strSourceName
> tdfNew.Connect = strODBCConnectString
> if <<strODBCConnectstring says that it is a trusted connection>> then
> tdfNew.Attributes = tdfNew.Attributes And (Not dbAttachSavePWD)
> else
> tdfNew.Attributes = tdfNew.Attributes Or dbAttachSavePWD
> end if
> dbsDao.TableDefs.Append tdfNew
>
> The special effect I meant is that if I open a linked table (itself, or a
> form that is bound to this table), then the currency columns show the
> value
> 0 instead of the correct values (which are mostly not 0). If we link the
> tables manually, all is OK!! An additional difficulty is that the effect
> was
> reported from several of our customers, but on NO one of our own PCs in
> our
> company we are able to reproduce the effect. We think that it must be some
> parameter like language of SQL server, language of windows, or I don't
> know
> how many properties or options there might be that I don't know of.
> Does any one have experienced the same thing, or have any idea?
>
>
|