Runtime error 3170.....Couldn't find installable ISAM

<br>
PSS ID Number: Q90111<br>
Article last modified on 11-18-1998<br>
<br>
2.0 7.0 97<br>
<br>
WINDOWS<br>
<br>
<br>
======================================================================<br>
<br>
---------------------------------------------------------------------<br>
The information in this article applies to:<br>
<br>
- Microsoft Access versions 2.0, 7.0, 97<br>
---------------------------------------------------------------------<br>
<br>
SYMPTOMS<br>
========<br>
<br>
Moderate: Requires basic macro, coding, and interoperability skills.<br>
<br>
If you try to import, export, or link (attach) a file by using an indexed<br>
sequential access method (ISAM) driver, you may receive an error message<br>
if Microsoft Access cannot find the ISAM driver.<br>
<br>
CAUSE<br>
=====<br>
<br>
ISAM drivers are used by Microsoft Access to update file formats other<br>
than its own.<br>
<br>
In Microsoft Access 2.0, if the path to the ISAM driver in your<br>
Msacc20.ini file is invalid, or if the ISAM driver does not exist, you may<br>
receive the following error message:<br>
<br>
Can't find installable ISAM.<br>
<br>
Microsoft Access 7.0 and 97 do not have an .ini file. Information<br>
previously stored in the .ini files is now stored in the Microsoft Windows<br>
Registry. In Microsoft Access 7.0 and 97, if the path to the ISAM driver<br>
in your Windows Registry is invalid, or if the ISAM driver does not exist,<br>
you may receive the following error message:<br>
<br>
Couldn't find installable ISAM.<br>
<br>
This error can also occur if you enter an invalid database name for a<br>
SQL database when you are using the TransferDatabase action in a macro.<br>
When you use an invalid connect string, Microsoft Access looks for an<br>
installable ISAM for the SQL database. If an installable ISAM cannot be<br>
located, an error occurs.<br>
<br>
RESOLUTION<br>
==========<br>
<br>
In Microsoft Access 2.0, edit the .ini file to specify the correct path in<br>
the [Installable ISAMs] section, or reinstall Microsoft Access using the<br>
Custom option. For troubleshooting tips related to this error message in<br>
Microsoft Access 2.0, please see the following article in the Microsoft<br>
Knowledge Base:<br>
<br>
ARTICLE-ID: Q150494<br>
TITLE : ACC2: Troubleshooting "Can't Find Installable ISAM" Error<br>
<br>
In Microsoft Access 7.0 or 97, you can edit the Windows Registry. For more<br>
information on registry changes, search for "Registry," and then<br>
"Customize Windows Registry settings used by Microsoft Access" using the<br>
Microsoft Access 97 Help index. For troubleshooting tips related to this<br>
error message in Microsoft Access 7.0, please see the following<br>
article in the Microsoft Knowledge Base:<br>
<br>
ARTICLE-ID: Q155666<br>
TITLE : ACC95: Troubleshoot "Couldn't Find Installable ISAM" Error<br>
<br>
For information about the ISAM drivers in Microsoft Access 97, please see<br>
the following article in the Microsoft Knowledge Base:<br>
<br>
ARTICLE-ID: Q159322<br>
TITLE : ACC97: Paradox, Lotus, & MS Exchange/Outlook ISAMs in<br>
ValuPack<br>
<br>
STATUS<br>
======<br>
<br>
This behavior is by design.<br>
<br>
MORE INFORMATION<br>
================<br>
<br>
Steps to Reproduce Behavior<br>
---------------------------<br>
<br>
1. Start Microsoft Access and open any database.<br>
<br>
2. Create a new macro called TestError:<br>
<br>
Macro Name Condition Action<br>
--------------------------------------<br>
TestError TransferDatabase<br>
<br>
TestError Actions<br>
----------------------------------------------------------------<br>
TransferDatabase<br>
Transfer Type: Link (or Attach in version 2.0)<br>
Database Type: ODBC Database (or SQL Database in version 2.0)<br>
Database Name: pubs<br>
Object Type: Table<br>
Source: dbo.authors<br>
Destination: Test<br>
Structure Only: No<br>
<br>
3. Save and run the macro. Note that you receive the error message. In<br>
this example, the invalid database name argument for a SQL database<br>
causes the error. To have the database name be valid, you must include<br>
the entire ODBC connection string for the attached SQL table.<br>
<br>
REFERENCES<br>
==========<br>
<br>
For more information about the TransferDatabase action, type<br>
"TransferDatabase" in the Office Assistant, click Search, and then click<br>
to view "TransferDatabase Action."<br>
======================================================================<br>
Keywords : OdbcOthr kberrmsg kbusage<br>
Version : 2.0 7.0 97<br>
Platform : WINDOWS<br>
Hardware : x86<br>
Issue type : kbprb<br>
=============================================================================<br>
Copyright Microsoft Corporation 1998.<br>
<br>
<br>
<br>