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 (283881)
The information in this article applies to:
- Microsoft Office Access 2003
- Microsoft Access 2002
This article was previously published under Q283881 Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry Moderate: Requires basic macro, coding, and interoperability
skills. This article applies to a Microsoft Access database (.mdb) and to a
Microsoft Access project (.adp). For a Microsoft Access
2000 version of this article, see
209805.
For a Microsoft Access
97 version of this article, see 90111.
SYMPTOMS 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. 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
not valid, or if the ISAM driver does not exist, you may receive one of the following
error messages: Error message 1 Could not find installable ISAM
Error message 2 The wizard is unable to access information
in the file '<pathname>'. Please check that the file exists and is the
correct format. RESOLUTIONWarning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. 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.
- Locate the relevant file in the following table.
|
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 |
- Use Windows Explorer to search for the file.
- If the file is found, record its path name; if it is not
found, proceed to step 9.
- Start Registry Editor.
- Browse to the registry subkey described in the table, and
check the path name against the actual path name.
- Correct the path name if it is incorrect; proceed with
these steps if it is correct.
- Quit Registry Editor. If you changed the path name, repeat
the process that produced the original error.
- If the error persists, or if the path name was correct in
step 6, rename the file.
- Start the Add/Remove Programs
tool.
- 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.
REFERENCESFor more information about editing the registry, type
registry in the Office Assistant, and then click Search to view the topics returned.
Modification Type: | Minor | Last Reviewed: | 11/30/2004 |
---|
Keywords: | kbupdateissue kberrmsg kbprb KB283881 kbAudDeveloper |
---|
|