When you import files, export files, or link files in Access 2002 or in Access 2003, some file types are missing, or you may receive a “Could not find installable ISAM” error message

When you import files, export files, or link files in Access, some file types are missing from the Files of type drop-down box in the Import dialog box , the Export dialog box , or the Link dialog box. 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.

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 not valid, or if the ISAM driver does not exist, you may receive one of the following error messages:

Error message 1Error message 2

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To correct the problem, you must correct path name errors in the 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.
   Collapse this tableExpand this 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. Start Registry Editor.
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. Quit 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.
10. Start the Office Setup program by clicking Change button against its entry in Add/Remove Programs and select the option to Repair or Reinstall Office.

For more information about editing the registry, type registry in the Office Assistant, and then click Search to view the topics returned.