Article ID: 240377 - View products that this article applies to.
This article was previously published under Q240377
This article details steps you can take to correct an installation problem with Microsoft Jet 3.51. It covers troubleshooting for DAO, ActiveX Data Objects (ADO), and ODBC access methods.
WARNING: This article contains specific information regarding editing the Windows Registry. You should always back up the registry before you edit it. If you alter the registry, you could cause your computer to stop functioning. Only an expert level programmer should attempt the steps in this article.
Microsoft provides this information without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with safe registry editing procedures.
If you have limited experience, you may want to contact a Microsoft Certified Partner. For more information about Microsoft Certified Partners, please see the following page on the World Wide Web:
http://www.microsoft.com/certpartner/For more information about the support options available from Microsoft, please see the following page on the World Wide Web:
IntroductionThe Microsoft Jet database engine is used by a wide variety of applications so it is possible that an application installation, or, more likely, an application uninstallation could adversely affect other applications on your computer. This article details steps you can take to make sure that Microsoft Jet is correctly installed on your computer.
The document is divided into three sections, (a) Troubleshooting the Access Method, which covers making sure the DAO, ADO, and ODBC drivers are installed correctly, (b) Troubleshooting Microsoft Jet, which covers the Jet DLLs and registry settings, and (c) Resource Data, which lists registry keys that would make the body of the article difficult to read.
Please see the following Microsoft Knowledge Base article for a continuation of this article, which includes Part C, the Resource Data:
(https://support.microsoft.com/kb/245524/EN-US/ )How To Ensure Jet 3.5 Is Installed Correctly (Part II)
Troubleshooting the Access MethodBefore troubleshooting the Jet installation, you need to make sure that the access method is correctly installed. The following sections cover DAO, ODBC, and ADO.
Data Access Objects (DAO)DAO is the most common Jet access method. The following steps can be used to make sure that it is properly installed:
Microsoft Access ODBC DriversInstalling Microsoft Access 2000, Microsoft Visual Basic 6.0 SP3, Microsoft Windows 2000, ADO 2.1 or later, and other products may break programs that use the Microsoft Access ODBC driver. These applications replace the Microsoft Jet 3.5 ODBC drivers with Microsoft Jet 4.0 ODBC drivers. These drivers have different capabilities and may cause your application to fail under certain circumstances. You can check the version numbers of the following files:
These files are located in your Windows\System (or Winnt\System32 for Windows NT) folder. The file version should start with 3.5 or 3.51.
Odbcjt32.dll Odbcji32.dll Odexl32.dll Oddbse32.dll Odpdx32.dll Odtext32.dll Odfox32.dll
If the version number starts with 4.0, then the following Microsoft Knowledge Base article deals specifically with this problem:
(https://support.microsoft.com/kb/237575/EN-US/ )Reverting to the Access 97 ODBC Driver After Installing MDAC
The article can also be used if the files do not exist at all. Once the drivers are in place, you should be able to view them in the ODBC Administrator in Control Panel (or Administrative Tools, if you are using Windows 2000), create DSNs to MDB and ISAM files, and compact a Microsoft Access database. If the article does not resolve the problem and you can use other ODBC drivers without experiencing a problem, continue to the Troubleshooting Microsoft Jet section.
ActiveX Data Objects (ADO)
Troubleshooting Microsoft JetIf you have reached this step, then you should be experiencing problems with Microsoft Access, the Microsoft Visual Basic data control, the VISDATA add-in, other applications, and your own DAO, RDO, and ADO code.
Core Jet Files
Jet DependenciesMicrosoft Jet has a number of file dependencies:
Older versions of the Oleaut32.dll file especially can be problematic. The Expsrv.dll file will not work properly with older versions. You can obtain the latest version of these DLLs by downloading the latest Microsoft Data Access Components from the Web. If you need the 3.5 version of the Microsoft Access ODBC drivers, you will have to restore them, as detailed in the Microsoft Access ODBC Drivers section earlier in the article, after upgrading the Microsoft Data Access Components.
Jet Installable ISAM DriversIf your application uses Jet 2.x or earlier MDB files, dBase files, Excel spreadsheets, or any of the other installable ISAM file formats, then you need to install one or more of the following files to the Windows\System (Winnt\System32 for Windows NT or Windows 2000) directory:
The registry keys are given in the Microsoft Jet Registry Settings section at the end of the article. Verify the registry keys exist. If not, the section gives instructions on creating them through a .reg file.
Msrd2x35.dll Jet 2.x IISAM Msexcl35.dll Excel IISAM Msexch35.dll Exchange IISAM Msltus35.dll Lotus 123 IISAM Mspdox35.Dll Paradox IISAM Mstext35.dll Text file IISAM Msxbse35.dll dBase/FoxPro IISAM
You can also register them with the following commands:
Regsvr32.exe C:\Windows\Msrd2x35.dll Regsvr32.exe C:\Windows\Msexcl35.dll Regsvr32.exe C:\Windows\Msexch35.dll Regsvr32.exe C:\Windows\Msltus35.dll Regsvr32.exe C:\Windows\Mspdox35.dll Regsvr32.exe C:\Windows\Mstext35.dll Regsvr32.exe C:\Windows\Msxbse35.dll
Jet ProfilesIf you use custom Jet profiles, the following article provides more information:
(https://support.microsoft.com/kb/173646/EN-US/ )How To Use a Custom Jet Profile to Alter Data Access Behavior
Article ID: 240377 - Last Review: July 1, 2004 - Revision: 2.4