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

Last reviewed: July 8, 1997
Article ID: Q90111

The information in this article applies to:

Microsoft Access versions 2.0, 7.0, 97

SYMPTOMS

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

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

CAUSE

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:

   Can'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 be caused by entering 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.

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:

   ARTICLE-ID: Q150494
   TITLE     : 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:

   ARTICLE-ID: Q155666
   TITLE     : 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:

   ARTICLE-ID: Q159322
   TITLE     : ACC97: Paradox, Lotus, & MS Exchange/Outlook ISAMs in
               ValuPack

STATUS

This behavior is by design.

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.

REFERENCES

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

Keywords : kberrmsg kbusage OdbcOthr
Version : 2.0 7.0 97
Platform : WINDOWS
Hardware : x86
Issue type : kbprb
Resolution Type : Info_Provided

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.