|
 |
access thread: Error 3170
Message #1 by "Richard Taylor" <richardt@g...> on Thu, 19 Jul 2001 09:58:10
|
|
Hi
Whenever I try and open a database which accesses linked tables, I get a
message "Couldn't find installable ISAM (Error 3170)". What is the problem?
I am getting this message on a new machine onto which I have loaded
existing databases.
Richard Taylor
Message #2 by Brian Skelton <brian.skelton@b...> on Thu, 19 Jul 2001 11:29:34 +0100
|
|
Are the linked tables in a mdb file? Or some other format?
If they're Excel of FoxPro tables (for example), I'd say you have a
corrupt or missing ISAM dll.
Look up Microsoft's Knowledge Base article Q155666 for a fix.
-BDS
-----Original Message-----
From: Richard Taylor [SMTP:richardt@g...]
Sent: 19 July 2001 10:58
To: Access
Subject: [access] Error 3170
Hi
Whenever I try and open a database which accesses linked tables, I get a
message "Couldn't find installable ISAM (Error 3170)". What is the
problem?
I am getting this message on a new machine onto which I have loaded
existing databases.
Richard Taylor
Message #3 by "Pardee, Roy E" <roy.e.pardee@l...> on Thu, 19 Jul 2001 07:58:06 -0700
|
|
I believe that the FoxPro ISAM is no longer included in A2K(!), so that's
something else to look into if you're using A2K. We had to switch to using
the .dbf ISAM for FoxPro tables. Supposedly the Visual FoxPro ODBC driver
works too--I've not tried it.
HTH,
-Roy
-----Original Message-----
From: Brian Skelton [mailto:brian.skelton@b...]
Sent: Thursday, July 19, 2001 3:30 AM
To: Access
Subject: [access] Error 3170
Are the linked tables in a mdb file? Or some other format?
If they're Excel of FoxPro tables (for example), I'd say you have a corrupt
or missing ISAM dll.
Look up Microsoft's Knowledge Base article Q155666 for a fix.
-BDS
-----Original Message-----
From: Richard Taylor [SMTP:richardt@g...]
Sent: 19 July 2001 10:58
To: Access
Subject: [access] Error 3170
Hi
Whenever I try and open a database which accesses linked tables, I get a
message "Couldn't find installable ISAM (Error 3170)". What is the problem?
I am getting this message on a new machine onto which I have loaded
existing databases.
Richard Taylor
|
|
|
View Cart
