PRB: FileMon Shows That DAO360.dll Fails to Load MSJet49.dll, MSJet48.dll, and Other MSJetxx.dll Files (306386)



The information in this article applies to:

  • Microsoft Data Access Components 2.1
  • Microsoft Data Access Components 2.1 (GA)
  • Microsoft Data Access Components 2.1 SP1
  • Microsoft Data Access Components 2.1 SP2
  • Microsoft Data Access Components 2.5
  • Microsoft Data Access Components 2.5 SP1
  • Microsoft Data Access Components 2.5 SP2
  • Microsoft Access 2000 Service Release 1 (SR-1)
  • Microsoft Access 2002
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP4
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP5

This article was previously published under Q306386

SYMPTOMS

When you use FileMon or another utility to monitor file activity, if an application uses DAO 3.6x with Jet 4.0, you receive the following error message:
FILE NOT FOUND
for the following dynamic-link libraries (DLLs):

MSJET49.DLL
MSJET48.DLL
MSJET47.DLL
MSJET46.DLL
MSJET45.DLL
MSJET44.DLL
MSJET43.DLL
MSJET42.DLL
MSJET41.DLL

However, you also notice that MSJET40.DLL is loaded successfully.

CAUSE

This behavior is by design to allow future Jet 4 functionality to be included into DLLs that are named incrementally. For example, a new version of Jet 4 can be implemented in a DLL named MSJET41.DLL. DAO 3.60 then automatically uses the new version of Jet 4, MSJET41.DLL.

Microsoft Development has found that it does not significantly impact DAO 3.60 or Jet 4.0 performance to load these DLLs.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Download and unzip FileMon from the following Sysinternals Web site:
  2. Run Filemon.exe, and notice that tracing starts immediately. Click the magnifying glass icon on the toolbar to stop the trace. To clear the display, click Clear Display on the Edit menu.
  3. In Visual Basic 6.0 Service Pack 4 or later, create a new Standard EXE project. Form1 is created by default.
  4. In FileMon, click the magnifying glass icon on the toolbar to start a new FileMon trace.
  5. In Visual Basic, add an intrinsic Data Control from the toolbox to Form1. Data1 is created by default.
  6. Set the properties of Data1 as follows:
    PropertyValue
    ConnectAccess 2000
    DatabaseNameSelect the NWind.MDB that comes with Visual Basic
    RecordSourceSelect Employees from the drop-down list box

  7. In FileMon, click the magnifying glass icon on the toolbar to end the FileMon trace.
  8. Scroll through the FileMon trace. Notice the file activity for MSJET49.dll, MSJET48.DLL, and so on.

Modification Type:MajorLast Reviewed:6/29/2004
Keywords:kbJET kbMDACNoSweep kbprb KB306386