Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 306386 - Last Review: December 26, 2006 - Revision: 4.3
PRB: FileMon Shows That DAO360.dll Fails to Load MSJet49.dll, MSJet48.dll, and Other MSJetxx.dll Files
This article was previously published under Q306386
When you use FileMon or another utility to monitor file activity, if an application uses DAO 3.6
x with Jet 4.0, you receive the following error message:
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.
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.
Steps to Reproduce Behavior
- Download and unzip FileMon from the following Sysinternals Web site:
- 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.
- In Visual Basic 6.0 Service Pack 4 or later, create a new Standard EXE project. Form1 is created by default.
- In FileMon, click the magnifying glass icon on the toolbar to start a new FileMon trace.
- In Visual Basic, add an intrinsic Data Control from the toolbox to Form1. Data1 is created by default.
- Set the properties of Data1 as follows:
Collapse this tableExpand this table
| Property | Value |
|---|
| Connect | Access 2000 |
| DatabaseName | Select the NWind.MDB that comes with Visual Basic |
| RecordSource | Select Employees from the drop-down list box |
- In FileMon, click the magnifying glass icon on the toolbar to end the FileMon trace.
- Scroll through the FileMon trace. Notice the file activity for MSJET49.dll, MSJET48.DLL, and so on.
APPLIES TO
- Microsoft Data Access Components 2.1
- Microsoft Data Access Components 2.1 Service Pack 2
- Microsoft Data Access Components 2.1 Service Pack 1
- Microsoft Data Access Components 2.1 Service Pack 2
- Microsoft Data Access Components 2.5
- Microsoft Data Access Components 2.5 Service Pack 1
- Microsoft Data Access Components 2.5 Service Pack 2
- Microsoft Access 2000 Service Pack 1
- Microsoft Access 2002 Standard Edition
- Microsoft Visual Basic 6.0 Enterprise Edition Service Pack 4
- Microsoft Visual Basic 6.0 Enterprise Edition Service Pack 5
| kbjet kbmdacnosweep kbprb KB306386 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate