ACC: "Couldn't Find Installable ISAM" Error Message

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q90111

Moderate: Requires basic macro, coding, and interoperability skills.

SYMPTOMS

If you try to import, export, or link (attach) a file by using an indexed sequential access method (ISAM) driver, you may receive an error message if Microsoft Access cannot find the ISAM driver.

Back to the top

ISAM drivers are used by Microsoft Access to update file formats other than its own.

In Microsoft Access 2.0, if the path to the ISAM driver in your Msacc20.ini file is invalid, or if the ISAM driver does not exist, you may receive the following error message:

Couldn't find installable ISAM.

Microsoft Access 7.0 and 97 do not have an .ini file. Information previously stored in the .ini files is now stored in the Microsoft Windows Registry. In Microsoft Access 7.0 and 97, if the path to the ISAM driver in your Windows Registry is invalid, or if the ISAM driver does not exist, you may receive the following error message:

Couldn't find installable ISAM.

This error can also occur if you enter an invalid database name for a SQL database when you are using the TransferDatabase action in a macro. When you use an invalid connect string, Microsoft Access looks for an installable ISAM for the SQL database. If an installable ISAM cannot be located, an error occurs.

Back to the top

RESOLUTION

In Microsoft Access 2.0, edit the .ini file to specify the correct path in the [Installable ISAMs] section, or reinstall Microsoft Access using the Custom option. For troubleshooting tips related to this error message in Microsoft Access 2.0, please see the following article in the Microsoft Knowledge Base:

150494 (http://support.microsoft.com/kb/150494/EN-US/ ) ACC2: Troubleshooting "Can't Find Installable ISAM" Error

In Microsoft Access 7.0 or 97, you can edit the Windows Registry. For more information on registry changes, search for "Registry," and then "Customize Windows Registry settings used by Microsoft Access" using the Microsoft Access 97 Help index. For troubleshooting tips related to this error message in Microsoft Access 7.0, please see the following article in the Microsoft Knowledge Base:

155666 (http://support.microsoft.com/kb/155666/EN-US/ ) ACC95: Troubleshoot "Couldn't Find Installable ISAM" Error

For information about the ISAM drivers in Microsoft Access 97, please see the following article in the Microsoft Knowledge Base:

159322 (http://support.microsoft.com/kb/159322/EN-US/ ) ACC97: Paradox, Lotus, & MS Exchange/Outlook ISAMs in ValuPack

Back to the top

STATUS

This behavior is by design.

Back to the top

MORE INFORMATION

Steps to Reproduce Behavior

Start Microsoft Access and open any database.

Create a new macro called TestError:

      Macro Name Condition  Action
      --------------------------------------
      TestError             TransferDatabase

      TestError Actions
      ----------------------------------------------------------------
      TransferDatabase
         Transfer Type: Link (or Attach in version 2.0)
         Database Type: ODBC Database (or SQL Database in version 2.0)
         Database Name: pubs
         Object Type: Table
         Source: dbo.authors
         Destination: Test
         Structure Only: No

Save and run the macro. Note that you receive the error message. In this example, the invalid database name argument for a SQL database causes the error. To have the database name be valid, you must include the entire ODBC connection string for the attached SQL table.

Back to the top

REFERENCES

For more information about the TransferDatabase action, type TransferDatabase in the Office Assistant, click Search, and then click to view "TransferDatabase Action."

Back to the top

APPLIES TO

Microsoft Access 2.0 Standard Edition
Microsoft Access 95 Standard Edition
Microsoft Access 97 Standard Edition

Back to the top

kberrmsg kbprb kbusage KB90111

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top