| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Jet Database Engine (All Languages) - 32-Bit Win
| Product Summary |
Product: Jet Database Engine
Version: |
Category: Compliant*
Operating System: 32-Bit Win |
| Language: All Languages |
Release Date: N/A |
| Operational Range: |
01 Jan 200 - 17 Jan 2038 |
| Prerequisites: |
See below |
| Product Dependencies: |
Windows 95, Windows 98, or Windows NT 3.51 x/Service Pack 5 or greater, or Windows NT4 (No specific service pack required, though Service Pack 2 is recommended). |
| Clock Dependencies: |
System Clock |
| Last Updated: |
03 Sep 1999 | |
| Product Details |
|
This document is applicable to versions: 3.0, 3.5, 3.51, 3.52, 4.0
Release Dates: 1995-1999
Prerequisites:
1) 3.0 remediation requires an existing 3.0 installation
2) 3.5x remediation requires an existing 3.5x installation
3) Year 2000 compliant MDAC because Jet utilizes MDAC's OLE DB Data Coercion Library
Hosting Products: Including, but not limited to û
3.0: Access95
3.5x: Access 97, Money 99, MDAC 1.5, Visual Studio 6.0, MDAC 2.0, MDAC 2.0 Service Pack 1, MDAC 2.0 Service Pack 2
4.0: MDAC 2.1, SQL Server 7.0, SQL Server 6.5 Service Pack 5
4.0 SP1: Office 2000, Access 2000, MDAC 2.1 Service Pack 1 (2.1.1.3711.11 GA)
, Visual Basic 6 Service Pack 3
The Microsoft Jet Database Engine ("Jet") is a component database engine utilized in various Microsoft products. The æengineÆ is composed of several components (Jet DLLs, Replication DLLs, Installable ISAM DLLs, etc.), plus an OLE DB provider and ODBC Driver. Customers obtain the Microsoft Jet Database Engine via these various Microsoft products. Microsoft also makes these components available via the web. Microsoft Jet year 2000 updates ("remediation") can be obtained via links supplied below. This document provides compliance information for Microsoft Jet releases versions 3.0 through 4.0. It includes information from the core component compliance documents.
Microsoft Jet ODBC Driver and OLE DB Provider notes:
Year 2000 compliance for the Microsoft Jet ODBC Driver is covered within the Microsoft Data Access Components (MDAC) year 2000 documentation. This can be found in the æData AccessÆ section of the Year 2000 Product Guide on the Microsoft Year 2000 Readiness Disclosure & Resource Center Web site at http://www.microsoft.com/technet/year2k/product/product.htm
The Microsoft OLE DB Provider for Microsoft Jet (MSJTOR35.DLL for Jet 3.5x, MSJetOLEDB40.DLL for Microsoft Jet 4.0) has no known inherent year 2000 issues. This component, however, has a dependency on the Microsoft OLEDB Data Coercion library that ships with MDAC. For latest compliance information on those components, please see the MDAC year2000 documentation referenced above.
The following table lists Microsoft Jet releases, compliance as originally released, and sources of update.
|
Jet Release |
Year |
Compliance as originally released |
Component containing Year 2000 issues (details below ) |
Remediation sources |
|
3.0
|
1995 |
Compliant# |
Note A - Jet Engine
Note B - Jet Replication
Note C - Text Import |
3.0 : MSJTWNG.EXE |
|
3.5
|
1996 |
Compliant# |
Note A - Jet Engine
Note B - Jet Replication |
3.51 Service Pack 3: Jet35sp3.EXE |
|
3.51
|
1997 |
Compliant# |
Note A - Jet Engine
Note B - Jet Replication |
3.51 Service Pack 3: Jet35sp3.EXE |
|
3.52
|
1997 |
Compliant# |
Note A - Jet Engine |
3.52 Service Pack 3 Jet35sp3.EXE |
|
4.0
|
1999 |
Compliant# |
Note A - Jet Engine |
4.0 Service Pack 1 - Office2000 and other various Microsoft applications, or 4.0 Service Pack 2 - MDAC 2.1 SP2 (2.1.2.4202.3 GA) or 4.0 Service Pack 3: Jet40sp3.EXE |
|
4.0 SP1, SP2 |
1999 |
Compliant |
|
|
How to determine which version of Jet is installed:
In general, to check the version of a file it is often easiest to use the Find (file) command in the Tools section of Windows Explorer. After selecting the file, right clicking allows you to examine the Properties which has a Version tab.
For Microsoft Jet overall, the key file to version check is Jet DLL, which is the core engine.
|
Jet version |
Jet DLL |
Version(s) |
Compliance |
|
3.0 |
Msjt3032.dll |
All < 3.000.4513 |
Compliant# |
|
3.0 remediated |
Msjt3032.dll |
All >= 3.000.4513 |
Compliant |
|
3.5 |
MsJet35.dll |
All < 3.51.2723.0 |
Compliant# |
|
3.5 remediated |
MsJet35.dll |
All >= 3.51.2723.0 |
Compliant via 3.51 remediated |
|
3.51 |
MsJet35.dll |
All < 3.51.2723.0 |
Compliant# |
|
3.51 remediated |
MsJet35.dll |
All>= 3.51.2723.0 |
Compliant |
|
3.52 |
Msjt4jlt.dll |
All < 3.52.2723.0 |
Compliant# |
|
3.52 remediated |
Msjt4jlt.dll |
All>= 3.52.2723.0 |
Compliant |
|
4.0 |
MsJet40.dll |
4.00.2115.25 |
Compliant# |
|
4.0 remediated |
MsJet40.dll |
All>= 4.00.2521.8 |
Compliant |
Note A: Jet Engine (Versions 3.0, 3.50, 3.51, 3.52, 4.0)
Background:
Windows 98 and Windows NT 4 (via the system registry) present users with the capability of adjusting the systemÆs interpretation of 2-digit dates via OLEAUT32.DLL versions 2.30 and above. This feature is sometimes referred to as the æSliding WindowÆ. This allows the user to dictate when 2-digit shortcut dates will be interpreted as dates in the 1900s or 2000s. (e.g. "1-1-29" is 1-1-1929 or 1-1-2029).
Related documentation:
http://www.microsoft.com/technet/year2k/white/auto.htm
http://www.microsoft.com/technet/year2k/white/offsol/offsol4.htm
Issue statement:
Prior to this update, when the Microsoft Jet engine stored queries coming from the Access Query Builder User Interface (æQBEÆ) containing a date restriction, Microsoft Jet stored the query with a literal 2-digit date. The 2-digit date was expanded to 4 digits when the query is executed. The translation to 4-digits comes through OLEAUT32 and is based upon the current Windows 98 or Windows NT 4 sliding window setting on that system. Therefore, the stored 2-digit date could be interpreted differently on systems with varying sliding window settings, resulting in unexpected query results.
Issue resolution:
Jet now stores 4-digit dates in stored QBE queries, based on that machines sliding window setting at the time the query is created or the date field is updated via the QBE.
Note B: Jet Replication (Versions 3.0, 3.50, 3.51)
The Jet 3.x expression service has some management issues in the MSysGenHistory and MSysExchangeLog tables. If a replica set was created in the 1900s, and is then compacted after January 1, 2000, databases that are members of the replica set may no longer be able to synchronize once the databases have been compacted.
Compacting removes Generation information from the MSysGenHistory table and exchange information from the MSysExchangeLog table. This information is needed for proper synchronization.
This issue may affect Jet 3.x replicated databases created before January 1, 2000 and compacted after January 1, 2000. The KB Article is referenced immediately below:
ACC97: No Common Point to Synchronize Replicas After Year 2000. Last reviewed: September 21, 1998 Article ID: Q191916
Note C: Text Import (Version 3.0)
The Microsoft Jet Engine text import facilities interpreted incoming 2-digit shortcut dates æ00Æ through æ29Æ to mean 1900-1929. This has been modified to interpret these dates as 2000-2029. | |
Return to Search Screen
| Legend of Symbols: |
| * |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
| # |
The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
| + |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
