Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 937248 - Last Review: May 29, 2008 - Revision: 4.2
Description of the Jet 4.0 Database Engine update rollup for the release version of Windows Vista: May 11, 2007
Notice
To resolve the problem that is discussed in this article,
upgrade to Windows Vista Service Pack 1. If you cannot upgrade to Windows Vista
Service Pack 1, be aware that Microsoft Knowledge Base article 943509
supersedes this current article, and the 943509 article contains a later
version of the Jet 4.0 hotfix.
For
more information, click the following article number to view the article in the
Microsoft Knowledge Base:
943509Â
(http://kbalertz.com/Feedback.aspx?kbNumber=943509/
)
Description of the Jet 4.0 Database Engine hotfix package for Windows XP Service Pack 2, Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2, Windows Vista, Windows Vista Service Pack 1, and Windows Server 2008: October 23, 2007
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.
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:
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:
Collapse this tableExpand this table
| 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:
Collapse this tableExpand this table
| 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.
This
hotfix is replaced by the hotfix that is described in the Microsoft Knowledge
Base article, 943509. To
resolve the problems that this article describes,apply the hotfix that is
described in Microsoft Knowledge Base article 943509.
For more information, click the following
article number to view the article in the Microsoft Knowledge Base:
943509Â
(http://kbalertz.com/Feedback.aspx?kbNumber=943509/
)
Description of the Jet 4.0 Database Engine hotfix package for Windows XP S, Windows Server 2003 S, Windows Server 2003 S, Windows Vista, Windows Vista S, and Windows Server 2008: October 23, 2007
For more information, click the
following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
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:
933452Â
(http://kbalertz.com/Feedback.aspx?kbNumber=933452/
)
An application that uses Microsoft Jet 4.0 may stop unexpectedly when you try to access back-end data in a Microsoft SQL Server-based database that is running on a Windows Server 2003 S-based server
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:
930620Â
(http://kbalertz.com/Feedback.aspx?kbNumber=930620/
)
Description of the Jet 4.0 Database Engine post-Windows XP S hotfix package: January 25, 2007
APPLIES TO
- Windows Vista Enterprise 64-bit Edition
- Windows Vista Business 64-bit Edition
- Windows Vista Business N 64-bit Edition
- Windows Vista Ultimate 64-bit Edition
- Windows Vista Home Premium 64-bit Edition
- Windows Vista Home Basic 64-bit Edition
- Windows Vista Home Basic N 64-bit Edition
- Windows Vista Enterprise
- Windows Vista Business
- Windows Vista Business N
- Windows Vista Ultimate
- Windows Vista Home Premium
- Windows Vista Home Basic
- Windows Vista Home Basic N
- Windows Vista Starter
- Microsoft Open Database Connectivity 4.21
- Microsoft OLE DB Provider for Jet 4.0
- Microsoft Access 2000 Standard Edition
- Microsoft Access 2002 Standard Edition
- Microsoft Office Access 2003
- Windows Internet Explorer 7
| kbvistasp1fix kbdatabase kbjet kbhotfixrollup kbfix kbqfe kbinfo KB937248 |
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
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please