Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Categories

Welcome to the new platform of Programmer's Heaven! We apologize for the inconvenience caused, if you visited us from a broken link of the previous version. The main reason to move to a new platform is to provide more effective and collaborative experience to you all. Please feel free to experience the new platform and use its exciting features. Contact us for any issue that you need to get clarified. We are more than happy to help you.

Database Error (3170: Couldn't find installable ISAM)

Mike BMike B Posts: 136Member
I had written 50% of a program, and it was time to run over to my mom's house for the week. I opened the project, and hit run. I didn't change anything. All the files are in the same folder. Anyway, I hit run, and I immeadietly get an error...3 lines into the code. I didn't get this error before, but now I do...

[code]
MousePointer = vbHourglass


datDTBDB(0).RecordSource = datDTBDB(0).Tag & " where quote=" & Chr(34) & "02-0001" & Chr(34)
'Just a query I thought of...
datDTBDB(0).Refresh

[/code]

datDTBDB(0).Refresh is hightlighted for where the error occured. Error number 3170: Couldn't find installable ISAM. I can't find anything in the MSDN files about it

What do I do?


----

Comments

  • lionblionb Posts: 1,688Member ✭✭
    : I had written 50% of a program, and it was time to run over to my mom's house for the week. I opened the project, and hit run. I didn't change anything. All the files are in the same folder. Anyway, I hit run, and I immeadietly get an error...3 lines into the code. I didn't get this error before, but now I do...
    :
    : [code]
    : MousePointer = vbHourglass
    :
    :
    : datDTBDB(0).RecordSource = datDTBDB(0).Tag & " where quote=" & Chr(34) & "02-0001" & Chr(34)
    : 'Just a query I thought of...
    : datDTBDB(0).Refresh
    :
    : [/code]
    :
    : datDTBDB(0).Refresh is hightlighted for where the error occured. Error number 3170: Couldn't find installable ISAM. I can't find anything in the MSDN files about it
    :
    : What do I do?
    :
    :
    : ----
    :
    That's what I found in the MSDN using SEARCH tab:

    Couldn't find installable ISAM. (Error 3170)


    The DLL for an installable ISAM file could not be found. This file is required for linking external tables (other than ODBC or Microsoft Jet database tables). The locations for all ISAM drivers are maintained in the Windows Registry. These entries are created automatically when you install your application. If you change the location of these drivers, you need to correct your application Setup program to reflect this change and make the correct entries in the Registry.

    Possible causes:

    An entry in the Registry is not valid. For example, this error occurs if you're using a Paradox external database and the Paradox entry points to a nonexistent directory or driver. Exit the application, correct the Windows Registry, and try the operation again.


    One of the entries in the Registry points to a network drive and that network is not connected. Make sure the network is available, and then try the operation again.

    There is one more article:

    ACC: "Couldn't Find Installable ISAM" Error Message
    Last reviewed: November 18, 1998
    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 by 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 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.


    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 : OdbcOthr kberrmsg kbusage
    Version : 2.0 7.0 97
    Platform : WINDOWS
    Hardware : x86
    Issue type : kbprb



Sign In or Register to comment.