This article describes a Jet 4.0 Database Engine update rollup for the release version of Windows Vista. This update rollup fixes several issues that are not documented in the Microsoft Knowledge Base.

Back to the top

This article describes the Microsoft Jet 4.0 Database Engine issues that are fixed in the Jet 4.0 Database Engine update rollup for the release version of Windows Vista. This update rollup is dated May 11, 2007.

Note This update rollup does not apply to Microsoft Office Access 2007.

For more information about the differences between the Jet database engine and the access control entry (ACE) database engine, see the Microsoft Developer Network (MSDN) blog. To do this, visit the following Microsoft Web site:

Back to the top

Issues that are fixed in this update rollup

The following issues are fixed in this update rollup but were not previously documented in a Microsoft Knowledge Base article:

•	On a Microsoft Windows Vista-based computer, you run programs that use the Microsoft Jet Database Engine. When you synchronize a database over the Internet, you may receive the following error message: Assertion failed! Program: … File: ..\COMMON\inc\safestrfuncs.h Line: … Expression: S_OK ==hr For information on how your program can cause and assertion failure, see the Visual C++ documentation on asserts (Press Retry to debug the application – JIT must be enabled) Additionally, if you click Abort or Retry, Microsoft Office Access closes. If you click Ignore, the same message appears repeatedly until the synchronization is complete. Note The "Assertion failed" error message may also appear outside database replication scenarios.
•	When you use the DAO Seek method on a Windows Vista-based computer, the function may not find a record that matches the criteria. This may occur even though there are matching values in the record set. You may experience this issue only if the following conditions are true: • The database that is queried is in Access 97 format. • The Windows system locale (language) is set to a language other than English. • The indexed column contains double-byte character set (DBCS) data. • The column and index were created by using the DAO Tabledefs method and not by using the SQL CREATE TABLE statement or the SQL CREATE INDEX statement. • A compaction or a repair of the database has not been performed since the column was created.
•	When you use a Jet 4.0 database that has links to an ODBC SQL database, you may receive an error message that resembles the following: Access has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Access. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you view the data that the error report contains, you see information about common error signatures. This information resembles the following: Application name Application version Module name Module version Offset Msaccess.exe 11.0.6566.0 Msjet40.dll 4.0.9635.0 Offset_Value This information may vary depending on the version of Access that you are running. The information may also vary depending on the program that you use as the front end for the Jet 4.0 database engine.
•	When you use Internet Explorer or Access, you may receive an error message that resembles the following: Application_Name has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Application_Name. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you view the data that the error report contains, you see information about common error signatures. This information resembles the following: Application name Application version Module name Module version Offset iexplore.exe 7.0.6000.16386 dao360.dll 3.60.9635.0 Offset_Value This information may vary depending on the program and on the version of the program.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply the hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The Global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x64-based versions

File name	File version	File size	Date	Time	Platform
Msrd2x40.dll	4.0.9635.0	323,584	11-May-2007	23:03	x86
Msrd3x40.dll	4.0.9702.0	344,064	11-May-2007	23:03	x86
Msjet40.dll	4.0.9702.0	1,589,248	11-May-2007	23:03	x86
Msrepl40.dll	4.0.9702.0	647,168	11-May-2007	23:03	x86
Mstext40.dll	4.0.9702.0	282,624	11-May-2007	23:03	x86
Msexcl40.dll	4.0.9702.0	344,064	11-May-2007	23:03	x86
Msexch40.dll	4.0.9702.0	413,696	11-May-2007	23:03	x86
Msltus40.dll	4.0.9702.0	245,760	11-May-2007	23:03	x86
Mspbde40.dll	4.0.9702.0	376,832	11-May-2007	23:03	x86
Msxbde40.dll	4.0.9702.0	450,560	11-May-2007	23:03	x86
Dao360.dll	3.60.9702.0	610,304	11-May-2007	23:03	x86
Msjetoledb40.dll	4.0.9702.0	368,640	11-May-2007	23:03	x86
Msjtes40.dll	4.0.9702.0	299,008	11-May-2007	23:03	x86

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Msrd2x40.dll	4.0.9635.0	323,584	11-May-2007	23:03	x86
Msrd3x40.dll	4.0.9702.0	344,064	11-May-2007	23:03	x86
Msjet40.dll	4.0.9702.0	1,589,248	11-May-2007	23:03	x86
Msrepl40.dll	4.0.9702.0	647,168	11-May-2007	23:03	x86
Mstext40.dll	4.0.9702.0	282,624	11-May-2007	23:03	x86
Msexcl40.dll	4.0.9702.0	344,064	11-May-2007	23:03	x86
Msexch40.dll	4.0.9702.0	413,696	11-May-2007	23:03	x86
Msltus40.dll	4.0.9702.0	245,760	11-May-2007	23:03	x86
Mspbde40.dll	4.0.9702.0	376,832	11-May-2007	23:03	x86
Msxbde40.dll	4.0.9702.0	450,560	11-May-2007	23:03	x86
Dao360.dll	3.60.9702.0	610,304	11-May-2007	23:03	x86
Msjetoledb40.dll	4.0.9702.0	368,640	11-May-2007	23:03	x86
Msjtes40.dll	4.0.9702.0	299,008	11-May-2007	23:03	x86

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

For more information about a similar fix for Microsoft Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base: For more information about a similar fix for Microsoft Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top