You receive a "Could not find installable ISAM" error message or some file types are missing when you import files, export files, or link files in Access 2000 (209805)
The information in this article applies to:
This article was previously published under Q209805 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 2002 version or a Microsoft
Office Access 2003 version of this article, see
283881. For a Microsoft Access 97 version of this article, see
90111. SYMPTOMSWhen you import files, export files, or link files in
Microsoft 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. You may receive the following error messages if Access
cannot find the indexed sequential access method (ISAM) driver for that type of
file: 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 that the file is in the correct format. You may also
receive these error messages if you are trying to import from, link to, and
export to Microsoft FoxPro from Access 2000. Access 2000 requires that you use
the Microsoft Visual FoxPro Open Database Connectivity (ODBC) driver. Access 97
uses an ISAM driver. This problem may occur when databases are upgraded from
Access 97 to Access 2000. For additional information about how
to set up the ODBC connection to the Visual FoxPro database, click the
following article number to view the article in the Microsoft Knowledge Base: 225861
No
option to import, link, or export to the FoxPro file type
CAUSE ISAM drivers are used by Access to update file formats
other than its own. If the path of the ISAM driver in your Windows Registry is
not valid, or if the ISAM driver does not exist, the problem may
occur.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 can try to register
the file manually or you must correct path name errors in the Windows Registry,
and then install or replace the problem file. To do this, follow these
steps. Note In error message 1 that is mentioned in the "Symptoms" section,
the file name is directly related to the attempted operation. In error message
2 that is mentioned in the "Symptoms" section, 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 Microsoft Windows Explorer to search for the
file.
- If the file is found, record the path name for the file. If
the file is not found, go to step 13.
- Open the Windows Registry Editor.
- Locate the registry subkey that is described in the table,
and then check the path name against the actual path name. If the registry key
does not exist, go to step 8.
- Correct the path if it is incorrect. Continue these steps
if the path is correct.
- Close Registry Editor.
If you changed the path,
repeat the process that produced the original error. - If the error persists, try to manually register the file by
using the Regsvr32.exe utility.
The Regsvr32.exe utility is an
application that is used to register DLLs and ActiveX Controls in the Windows
Registry. You can use this file to stop the issue of mismatched .dll files. To
re-register your .dll files by using the Regsvr32.exe utility, go to the next
step. - Verify that the Regsvr32.exe file is in the system folder
where Windows is installed.
For example, the Regsvr32.exe file is
typically found in C:\Windows\System or in C:\Winnt\System32. - Click Start, and then click
Run.
- In the Run dialog box, type the following
command in the Open box.
Note The path of Regsvr32.exe and the name and the path of the DLL may
be different on your computer. The following command registers the Excel
ISAM:
Regsvr32
c:\winnt\system32\msexcl40.dll
Note Another method of registering DLLs is to use Windows Explorer to
find the DLL.
Double-click the DLL. In the Open With
dialog box, click Regsvr32.exe, and then click
OK.
This creates a permanent association of all DLLs
with Regsvr32.exe. You can register other unregistered DLLs by double-clicking
them.
For additional information about how to obtain this file,
click the following article number to view the article in the Microsoft
Knowledge Base: 267279
Regsvr32.exe available in Download Center
- If the error persists, or if the path name was correct in
step 5, rename the file.
- Start the Add/Remove Programs tool, start the Office 2000
Setup program, and then click Repair Office.
REFERENCESFor 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. For
additional information about importing, linking, or exporting to the FoxPro
file type, click the following article number to view the article in the
Microsoft Knowledge Base: 225861
No option to import, link, or export to the FoxPro file type
Modification Type: | Minor | Last Reviewed: | 8/12/2004 |
---|
Keywords: | kbRegistry kbExport kbImport kbopenfile kberrmsg kbprb KB209805 kbAudDeveloper |
---|
|