A
Al Danks
The problem occurs on multiple computers with Access XP,
Windows 2000 or Windows XP.
We have an Access XP database with external links via ODBC
(Intersolv 3.11) to some network (Novell) resident Paradox
tables. Everything was working fine and then suddenly we
get an ODBC error when attempting to open the linked
tables. (Just double-clicking on the linked table icon in
the Tables tab - nothing fancy.)
Here's where it gets interesting.
The same ODBC DSN/driver works fine in Access 97 on the
same computer.
The same ODBC DSN/driver works fine in Access 2000 on the
same computer. (If, however, we open the Access 2000
database in Access XP - ODBC error.)
The problem first happened on Wednesday - only on my
computer. I did a Detect and Repair and the error message
changed to one telling me that the Paradox table did not
exist at L:\Databases. The ODBC DSN directory is
L:\Databases\CAMSDATA. So Access XP / ODBC was not looking
for the table in the correct location. I relinked the
tables and all was well until this afternoon.
The ODBC error that the Paradox table does not exist
reappeared around 2:20pm. (It was working fine at 2:05pm.)
This time the error occurs on multiple machines. The very
curious thing is that the error says the Paradox table
does not exist - in the Access XP DEFAULT DATABASE FOLDER
(Tools | Options | General | Default database folder.) On
my pc it is l:\databases, on others it is C:\documents and
settings...
Somehow Access XP is losing it with the Paradox ODBC and
is looking for the table in the default database folder
instead of the directory indicated in the ODBC DSN.
(e-mail address removed)
Windows 2000 or Windows XP.
We have an Access XP database with external links via ODBC
(Intersolv 3.11) to some network (Novell) resident Paradox
tables. Everything was working fine and then suddenly we
get an ODBC error when attempting to open the linked
tables. (Just double-clicking on the linked table icon in
the Tables tab - nothing fancy.)
Here's where it gets interesting.
The same ODBC DSN/driver works fine in Access 97 on the
same computer.
The same ODBC DSN/driver works fine in Access 2000 on the
same computer. (If, however, we open the Access 2000
database in Access XP - ODBC error.)
The problem first happened on Wednesday - only on my
computer. I did a Detect and Repair and the error message
changed to one telling me that the Paradox table did not
exist at L:\Databases. The ODBC DSN directory is
L:\Databases\CAMSDATA. So Access XP / ODBC was not looking
for the table in the correct location. I relinked the
tables and all was well until this afternoon.
The ODBC error that the Paradox table does not exist
reappeared around 2:20pm. (It was working fine at 2:05pm.)
This time the error occurs on multiple machines. The very
curious thing is that the error says the Paradox table
does not exist - in the Access XP DEFAULT DATABASE FOLDER
(Tools | Options | General | Default database folder.) On
my pc it is l:\databases, on others it is C:\documents and
settings...
Somehow Access XP is losing it with the Paradox ODBC and
is looking for the table in the default database folder
instead of the directory indicated in the ODBC DSN.
(e-mail address removed)