ACC2000: "Could Not Find Installable ISAM" Error Message

• Microsoft Access 2000

SYMPTOMS

If you try to import, export, or link 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 Access to update file formats other than its own. 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 messages:

Could not find installable ISAM

-or-

The wizard is unable to access information in the file '<pathname>'. Please check that the file exists and is the correct format.

RESOLUTION

To correct the problem, you need to correct path name errors in the Windows Registry, and install or replace the problem file.

In the case of the first error message, the file name is directly related to the attempted operation.

In the case of the second error message, the file name is mentioned in the text of the message.

1. Locate the relevant file in the following table.
   
   

   File Name	Import/Export ISAM for:	Windows Registry
   Msexcl40.dll	Microsoft Excel	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
   Msexch40.dll	Microsoft Exchange	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Exchange
   Msrd2x40.dll	Microsoft Jet 2.x	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 2.x
   Msrd3x40.dll	Microsoft Jet 3.x	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 3.x
   Msltus40.dll	Lotus 1-2-3	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Lotus
   Mspbde40.dll	Imprise Paradox	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Paradox
   Mstext40.dll	Text	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Text
   Msxbde40.dll	dBase	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Xbase




2. Use Windows Explorer to search for the file.



3. If the file is found, record its path name; if it is not found, proceed to step 9.



4. Open the Windows Registry Editor.
   
   WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
   
   For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).
   



5. Browse to the registry subkey described in the table, and check the path name against the actual path name.



6. Correct the path name if it is incorrect; proceed with these steps if it is correct.



7. Close the Registry Editor. If you changed the path name, repeat the process that produced the original error.



8. If the error persists, or if the path name was correct in step 6, rename the file.



9. Start the Add/Remove Programs tool, start the Office 2000 Setup program, and select the Repair Office option.

REFERENCES

For more information about editing the Windows Registry, click Microsoft Access Help on the Help menu, type Registry in the Office Assistant or the Answer Wizard, and then click Search to view the topics returned.

Additional query words: prb

Keywords : kberrmsg kbdta IsmGnrl
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbprb