How To Ensure Jet 3.5 Is Installed Correctly (Part I)

Introduction

Troubleshooting the Access Method

Data Access Objects (DAO)

1. Make sure you have the following file:

   C:\Program Files\Common Files\Microsoft Shared\Dao\Dao350.dll
   					

   NOTE: The drive letter may be different if your copy of Windows is installed on a drive other than drive C:.
   
   
2. If your project references the Microsoft DAO 2.5/3.5 (or 3.51) Compatibility Library instead of the Microsoft DAO 3.5 (or 3.51) Library, then you need to make sure the following file is installed:

   C:\Program Files\Common Files\Microsoft Shared\Dao\Dao2535.tlb
   					

3. You need to make sure that the registry keys for DAO exist. The registry keys are listed in the Microsoft DAO Registry Settings section later in this article. Use the RegEdit program to verify that the registry keys exist. If the registry keys are missing or pointing to a nonexistent file, you can manually unregister and re-register the Dao350.dll file by running the following two commands from the Windows Start button, and then select Run or from the MS/DOS command prompt use this command:

   Regsvr32.exe /U 
   "C:\Program Files\Common Files\Microsoft Shared\Dao\Dao350.dll"
   
   Regsvr32.exe
   "C:\Program Files\Common Files\Microsoft Shared\Dao\Dao350.dll"
   						

   Note that the earlier two commands have a line break for readability. You should run each command on one continuous line.
   
   Alternately, you can edit the registry directly. Instructions for applying the values through a .reg file are given in the Microsoft DAO Registry Settings section.
4. Once the file and registry settings are in place, you can test the DAO installation through code. Make a reference to the Microsoft DAO 3.5 (or 3.51) Library in your project and run the following statement:

   Debug.Print DBEngine.Version
   						

   If the statement works, yet your application still fails, you should continue with the "Troubleshooting Microsoft Jet" section.
   
   If the preceding test code causes this run-time error message:
   '429': ActiveX component can't create object.
   check to see if the DAO design-time license key exists on your computer. The following three lines may be saved to a file with the .reg extension and imported into the registry through the RegEdit program:

   REGEDIT4
   [HKEY_CLASSES_ROOT\Licenses\F4FC596D-DFFE-11CF-9551-00AA00A3DC45]
   @="mbmabptebkjcdlgtjmskjwtsdhjbmkmwtrak"
   					

5. If the code fails with an access violation, some of the support files may be out of date, typically:

   Oleaut32.dll
   Msvcrt.dll
   					

   The latest version of these files can be obtained by installing the latest version of:
   http://msdn.microsoft.com/en-us/data/aa937729.aspx Microsoft Data Access Components (MDAC)
   from the World Wide Web. Run it on your computer to install the latest support files.
   
   NOTE: Installing this file may overwrite the Microsoft Access ODBC drivers as outlined in the following section. If you have programs that use these drivers, you should be cautious about upgrading them.
   
   
6. Occasionally, an access violation may result from a mismatch between the version of Dao350.dll and some of the other Jet or support DLLs. For example, if you have a 3.50 version of Dao350.dll and Jet 3.51, you might have problems. Upgrading to a 3.51 version of Dao350.dll might help.

Microsoft Access ODBC Drivers

Odbcjt32.dll 
Odbcji32.dll 
Odexl32.dll
Oddbse32.dll 
Odpdx32.dll 
Odtext32.dll 
Odfox32.dll
				

ActiveX Data Objects (ADO)

1. First verify that you can use ADO with a provider other than the OLEDB Provider for Microsoft Jet. If not, then you need to verify that ADO is properly installed and registered. The following Microsoft Knowledge Base article helps you to troubleshoot the Microsoft Data Access Components:
   
   
   232060 How To MDAC Setup Troubleshooting Guide
   After ADO is installed and working properly proceed with the following steps to verify that the OLEDB provider for Microsoft Jet is properly installed and registered.
2. The OLEDB provider for Microsoft Jet 3.5 consists of the following two files:

   C:\Windows\System\Msjt4jlt.dll     (Winnt\System32 for Windows NT or Windows 2000)
   C:\Program Files\Common Files\System\Ole Db\Msjtor35.dll
   						

   Msjt4jlt.dll is Jet 3.52, a special version of Jet 3.5 specifically for ADO. It does not support linked files, stored queries, or the Installable ISAM drivers. It does rely on some of the other Jet 3.51 core files, specifically Msjter35.dll and Msjint35.dll, also located in the system directory.
   
   If these files do not exist, you can obtain them by downloading MDAC 2.0 from the following location on the Web, or from Visual Basic 6.0 (versions prior to SP3). MDAC 2.1 and later do not contain these files.
   
   If you do not have MDAC 2.1 or later on your computer, you can download the MDAC 2.0 version of the MDAC_TYP.exe file and run it to install these components. This MDAC 2.0 version of the MDAC_TYP.EXE file can be found at the following location:
   http://microsoft.com/data/download_20300223.htm
   If you do have a 2.1 or later version of MDAC on your computer, copy the MDAC 2.0 MDAC_TYP.exe file to a clean directory and run the following command: mdac_typ.exe /c /t:C:\MDAC20 This extracts the files into the C:\Mdac20 folder without installing them on your system. You can then copy the Msjt4jlt.dll and Msjtor35.dll files from this location to the directories indicated below in the REGSVR32 commands.
3. Register the files in the following order:

   Regsvr32.exe C:\Windows\System\Msjt4jlt.dll  (Winnt\System32 for Windows NT or Windows 2000)
   
   Regsvr32.exe "C:\Program Files\Common Files\System\Ole Db\Msjtor35.DLL"
   						

   If these steps do not resolve the problem, continue with the Troubleshooting Microsoft Jet section.

Troubleshooting Microsoft Jet

Core Jet Files

1. In order for Microsoft Jet to operate, you need a minimum of the following files installed on your computer, all in the C:\Windows\System directory (Winnt\System32 for Windows NT or Windows 2000):

   Msjet35.dll
   Msjter35.dll
   Msjint35.dll
   Vbajet32.dll
   Expsrv.dll       (this was introduced with Vbajet32.dll 6.x versions)
   					

2. The Microsoft Jet 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.
3. After completing these steps, you should be able to use Microsoft Jet to open Microsoft Jet 3.x database files. If you still have problems, some of the dependencies may be out of date. You can update them as detailed in the next section.

Jet Dependencies

Msvcrt.dll
Oleaut32.dll
				

Jet Installable ISAM Drivers

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
				

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 Profiles