This article describes the Microsoft Jet 4.0 Database Engine issues that are fixed in the Jet 4.0 Database Engine post-837001 hotfix package. This hotfix is dated May 11, 2006.

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

Consider the following scenario. You create a query against a linked SQL Server table where the left join is an inner join on itself. In this scenario, when you try to run the query, you receive an error message that resembles the following: ODBC--Call Failed. [Microsoft][ODBC SQL Server Driver][SQL Server] The column prefix 'name' does not match with a table name or alias name used in the query. (#107)

When you use the Jet 4.0 database on a multi-processor computer or a hyper-threaded computer, you 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 the following list that contains information about some of the most common error signatures. This information may vary depending on the version of Access or the application that you use as the front end for the Jet 4.0 database engine. Application Name Application Version Module Name Module Version Offset msaccess.exe 11.0.6566.0 msjet40.dll 4.0.8015.0 000130ba msaccess.exe 11.0.6355.0 msjet40.dll 4.0.8015.0 00004284 msaccess.exe 11.0.6355.0 msjet40.dll 4.0.8015.0 00004bf7 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.8015.0 00005346 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.8015.0 00004bf7 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.8015.0 000050f2 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.8015.0 000050f4 msaccess.exe 10.0.4302.0 msjet40.dll 4.0.8015.0 00005007 msaccess.exe 10.0.4302.0 msjet40.dll 4.0.8015.0 00004bf9

When you use a Jet 4.0 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 the following list that contains information about some of the most common error signatures. This information may vary depending on the version of Access or the application that you use as the front end for the Jet 4.0 database engine. Application Name Application Version Module Name Module Version Offset msaccess.exe 11.0.6566.0 msjet40.dll 4.0.9025.0 0003a585 msaccess.exe 11.0.6355.0 msjet40.dll 4.0.9025.0 0003a585 msaccess.exe 11.0.6355.0 msjet40.dll 4.0.8015.0 00039b23 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.9025.0 0003a585 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.8015.0 00039b23 msaccess.exe 10.0.6501.0 msjet40.dll 4.0.9025.0 0003a585 msaccess.exe 10.0.4302.0 msjet40.dll 4.0.8015.0 00039b23 msaccess.exe 10.0.4302.0 msjet40.dll 4.0.9025.0 0003a585

When you use a Jet 4.0 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 the following list that contains information about some of the most common error signatures. This information may vary depending on the version of Access or the application that you use as the front end for the Jet 4.0 database engine. Application Name Application Version Module Name Module Version Offset msaccess.exe 11.0.6566.0 msjet40.dll 4.0.9025.0 0004dff2 msaccess.exe 11.0.6355.0 msjet40.dll 4.0.9025.0 0004dff2 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.9025.0 0004dff2 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.8015.0 0004d7b9 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.8015.0 000b2c7b msaccess.exe 10.0.6501.0 msjet40.dll 4.0.9025.0 0004dff2 msaccess.exe 10.0.4302.0 msjet40.dll 4.0.8015.0 0004d7b9 msaccess.exe 10.0.4302.0 msjet40.dll 4.0.8015.0 000b2c7b

When you use a Jet 4.0 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 the following list that contains information about some of the most common error signatures. This information may vary depending on the version of Access or the application that you use as the front end for the Jet 4.0 database engine. Application Name Application Version Module Name Module Version Offset jetcomp.exe 4.0.1532.0 msjet40.dll 4.0.8618.0 0004e16f msaccess.exe 11.0.6566.0 msjet40.dll 4.0.8618.0 0004e16f msaccess.exe 11.0.6355.0 msjet40.dll 4.0.8618.0 0004e16f msaccess.exe 11.0.6355.0 msjet40.dll 4.0.8618.0 0 msaccess.exe 11.0.5614.0 msjet40.dll 4.0.8618.0 0004e16f msaccess.exe 10.0.6501.0 msjet40.dll 4.0.8618.0 0004e16f msaccess.exe 10.0.4302.0 msjet40.dll 4.0.8618.0 0004e16f

The Citrix Independent Management Architecture (IMA) service experiences an access violation in the Msjet40.dll file on a Microsoft Windows Server 2003 x64-based computer in a 32-bit or WOW64 process.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft Windows Server 2003 hotfix information

Prerequisites

To install this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or security update 837001 installed on your computer. For more information about how to obtain the latest service pack for Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base: Security update 837001 is described in security bulletin MS04-014. For more information about security bulletin MS04-014, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

If you use the Jet 4.0 database engine, you must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces security update 837001 and other Jet 4.0 service packs.

File information

The English 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 Server 2003, Itanium-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Wdao360.dll	3.60.9420.0	551,640	10-May-2006	15:45	x86	None	WOW
Wmsexcl40.dll	4.0.9025.0	326,360	10-May-2006	15:45	x86	None	WOW
Wmsjet40.dll	4.0.9425.0	1,514,272	10-May-2006	15:45	x86	None	WOW
Wmsjtes40.dll	4.0.9424.0	248,608	10-May-2006	15:45	x86	None	WOW
Wmspbde40.dll	4.0.9025.0	355,032	10-May-2006	15:45	x86	None	WOW
Wmsrepl40.dll	4.0.9025.0	552,991	10-May-2006	15:45	x86	None	WOW
Wmswdat10.dll	4.0.9422.0	838,432	10-May-2006	15:45	x86	None	WOW
Wmswstr10.dll	4.0.9422.0	621,344	10-May-2006	15:45	x86	None	WOW
Wmsxbde40.dll	4.0.9025.0	355,032	10-May-2006	15:45	x86	None	WOW
Wdao360.dll	3.60.9420.0	551,640	10-May-2006	15:48	x86	SP1	WOW
Wmsjet40.dll	4.0.9425.0	1,514,272	10-May-2006	15:48	x86	SP1	WOW
Wmsjtes40.dll	4.0.9424.0	248,536	10-May-2006	15:48	x86	SP1	WOW
Wmswdat10.dll	4.0.9422.0	838,360	10-May-2006	15:48	x86	SP1	WOW
Wmswstr10.dll	4.0.9422.0	621,272	10-May-2006	15:48	x86	SP1	WOW

Windows Server 2003, x64-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Wdao360.dll	3.60.9420.0	551,640	10-May-2006	15:48	x86	SP1	WOW
Wmsjet40.dll	4.0.9425.0	1,514,272	10-May-2006	15:48	x86	SP1	WOW
Wmsjtes40.dll	4.0.9424.0	248,536	10-May-2006	15:48	x86	SP1	WOW
Wmswdat10.dll	4.0.9422.0	838,360	10-May-2006	15:48	x86	SP1	WOW
Wmswstr10.dll	4.0.9422.0	621,272	10-May-2006	15:48	x86	SP1	WOW

Windows Server 2003, x86-based versions

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Dao360.dll	3.60.9420.0	551,640	23-Nov-2005	20:33	x86	None	RTMQFE
Msexcl40.dll	4.0.9025.0	326,360	21-Jun-2005	00:21	x86	None	RTMQFE
Msjet40.dll	4.0.9425.0	1,514,272	09-May-2006	22:19	x86	None	RTMQFE
Msjtes40.dll	4.0.9424.0	248,608	09-May-2006	22:19	x86	None	RTMQFE
Mspbde40.dll	4.0.9025.0	355,032	21-Jun-2005	00:21	x86	None	RTMQFE
Msrepl40.dll	4.0.9025.0	552,991	10-May-2006	23:19	x86	None	RTMQFE
Mswdat10.dll	4.0.9422.0	838,432	09-May-2006	22:19	x86	None	RTMQFE
Mswstr10.dll	4.0.9422.0	621,344	09-May-2006	22:19	x86	None	RTMQFE
Msxbde40.dll	4.0.9025.0	355,032	10-May-2006	15:44	x86	None	RTMQFE
Dao360.dll	3.60.9420.0	551,640	23-Nov-2005	20:31	x86	SP1	SP1QFE
Msjet40.dll	4.0.9425.0	1,514,272	10-May-2006	23:00	x86	SP1	SP1QFE
Msjtes40.dll	4.0.9424.0	248,536	10-May-2006	23:00	x86	SP1	SP1QFE
Mswdat10.dll	4.0.9422.0	838,360	13-Jan-2006	23:16	x86	SP1	SP1QFE
Mswstr10.dll	4.0.9422.0	621,272	13-Jan-2006	23:16	x86	SP1	SP1QFE

Microsoft Windows XP hotfix information

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

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To install this hotfix, you must have Windows XP Service Pack 2 (SP2) or security update 837001 installed on your computer. For more information about how to obtain the latest service pack for Windows XP, click the following article number to view the article in the Microsoft Knowledge Base: Security update 837001 is described in security bulletin MS04-014. For more information about security bulletin MS04-014, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

If you use the Jet 4.0 database engine, you must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces security update 837001 and other Jet 4.0 service packs.

File information

The English 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.

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Dao360.dll	3.60.9420.0	551,640	23-Nov-2005	20:38	x86	SP1	SP1QFE
Msexcl40.dll	4.0.9025.0	326,360	20-Nov-2005	05:33	x86	SP1	SP1QFE
Msjet40.dll	4.0.9425.0	1,514,272	11-May-2006	07:53	x86	SP1	SP1QFE
Msjtes40.dll	4.0.9424.0	248,608	11-May-2006	07:53	x86	SP1	SP1QFE
Mspbde40.dll	4.0.9025.0	355,032	19-Nov-2005	17:03	x86	SP1	SP1QFE
Msrepl40.dll	4.0.9025.0	552,991	12-May-2006	08:13	x86	SP1	SP1QFE
Mswdat10.dll	4.0.9422.0	838,432	11-May-2006	07:53	x86	SP1	SP1QFE
Mswstr10.dll	4.0.9422.0	621,344	11-May-2006	07:53	x86	SP1	SP1QFE
Msxbde40.dll	4.0.9025.0	355,032	20-Nov-2005	05:33	x86	SP1	SP1QFE
Dao360.dll	3.60.9420.0	551,640	16-Jan-2006	18:48	x86	SP2	SP2QFE
Msexcl40.dll	4.0.9025.0	326,360	16-Jan-2006	18:49	x86	SP2	SP2QFE
Msjet40.dll	4.0.9425.0	1,514,272	09-May-2006	09:15	x86	SP2	SP2QFE
Msjtes40.dll	4.0.9424.0	248,536	09-May-2006	09:15	x86	SP2	SP2QFE
Mspbde40.dll	4.0.9025.0	355,032	16-Jan-2006	18:49	x86	SP2	SP2QFE
Msrepl40.dll	4.0.9025.0	552,991	12-May-2006	08:46	x86	SP2	SP2QFE
Mswdat10.dll	4.0.9422.0	838,360	16-Jan-2006	18:49	x86	SP2	SP2QFE
Mswstr10.dll	4.0.9422.0	621,272	16-Jan-2006	18:49	x86	SP2	SP2QFE
Msxbde40.dll	4.0.9025.0	355,032	16-Jan-2006	18:49	x86	SP2	SP2QFE

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

For more information about how to upgrade to the latest Jet 4.0 service pack, click the following article number to view the article in the Microsoft Knowledge Base: For additional information, click the following article number to view the article in the Microsoft Knowledge Base: