Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Internet Explorer Admin Kit 5.0 (Slovak)
| 01 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| Internet Explorer 5 | ||
| System Clock | ||
| 21 Jul 1999 | ||
|
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer teams have tested operation with popular web servers and proxy servers, verification of the IEAK should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their year 2000 status and recommendations.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Explorer Admin Kit 5.0 (Spanish)
| 01 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| Internet Explorer 5 | ||
| System Clock | ||
| 21 Jul 1999 | ||
|
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer teams have tested operation with popular web servers and proxy servers, verification of the IEAK should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their year 2000 status and recommendations.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Explorer Admin Kit 5.0 (Swedish)
| 01 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| Internet Explorer 5 | ||
| System Clock | ||
| 21 Jul 1999 | ||
|
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer teams have tested operation with popular web servers and proxy servers, verification of the IEAK should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their year 2000 status and recommendations.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Explorer Admin Kit 5.0 (Turkish)
| 01 Jan 1980 - 31 Dec 2035 | ||
| none | ||
| Internet Explorer 5 | ||
| System Clock | ||
| 21 Jul 1999 | ||
|
This document pertains to Internet Explorer Administration Kit (IEAK) version 5. How the product handles dates: Dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Two-digit shortcut handling: The Internet Explorer Administration Kit does not use 2-digit Dates. Testing guidelines and recommendations: Tests of the Internet Explorer Administration Kit and customized packages generated by it for the year 2000 need to have the Internet Explorer Administration Kit, the server, the clients, and if applicable, proxy server, all transition to and operate in the year 2000 under testing. For example, depending on your web and proxy server, it may use a 2-digit year in its HTTP/1.0 headers. While the Internet Explorer teams have tested operation with popular web servers and proxy servers, verification of the IEAK should include testing of the below items within your corporate environment.
In addition, contact your web server and proxy server vendor for their year 2000 status and recommendations.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Arabic)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Chinese - Simplified)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Chinese - Traditional)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Czech)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Danish)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Dutch)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (English)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Finnish)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (French)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (German)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Hebrew)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Hungarian)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Italian)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Japanese)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Korean)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Norwegian)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Pan-Chinese)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Polish)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Portuguese (Brazil))
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Russian)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Spanish)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Swedish)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Internet Information Server (Thai)
| - | ||
| 11 Nov 1999 | ||
|
This component is an integral part of Windows NT. Please see the Windows NT Server 4, SP4, SP5 and SP6 compliance documents or the Windows NT Workstation 4, SP4, SP5 and SP6 compliance documents for further information. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Jet Database Engine (All Languages)
| 01 Jan 200 - 17 Jan 2038 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This document is applicable to versions: 3.0, 3.5, 3.51, 3.52, 4.0Release Dates: 1995-1999 Prerequisites: 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.htmThe 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.
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.
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.htmIssue 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 3.1 (English)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 29 Oct 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://www.microsoft.com/sitebuilder/magazine/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Arabic)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Catalan)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Chinese - Simplified)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Chinese - Traditional)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Czech)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Danish)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Dutch)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (English)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Finnish)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (French)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (German)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Greek)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Hebrew)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Hungarian)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Italian)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Japanese)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Korean)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Norwegian)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Polish)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Portuguese (Brazil))
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Portuguese)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Russian)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Slovak)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Slovenian)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Spanish)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Swedish)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
JScript 5.0 (Turkish)
| - | ||
| awareness of obsolete GetYear() function | ||
| System Clock | ||
| 04 Nov 1999 | ||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes Operational Range for Data: from 1/1/1970 forward or backward 285,616 years. How the product runtime handles dates: JScript stores dates internally as 4-digit years. Developers should take care to enter dates in four-digit format, and to verify that dates entered by end users are interpreted as they expect. Two-digit shortcut handling: The JSCRIPT method .getYear() returns a 2-digit string for years within the operational range up to 1999. The method returns a 4-digit string for years within the operational range from 2000. Web authors can use the method .getFullYear(), which returns 4-digit dates. The JSCRIPT function Date() interprets mm/dd/00 as 1900. If the Date() function is used with mm/dd/2000 it will return 2000. Recommended practices to develop year 2000 compliant applications: See http://msdn.microsoft.com/workshop/languages/clinic/y2kscript.asp for suggestions.Common development errors dealing with year 2000 date issues: JScript developers should be aware that the GetYear() function is not Year 2000 compliant. This is in accordance with the specifications and older versions of JScript and Netscape’s JavaScript. Developers who want the functionality provided by this function should use GetFullYear() instead. Recommended developer action: Developers must be aware of this issue to write compliant applications. Using the obsolete GetYear() function when the desired behavior is given by the GetFullYear() function could cause developers to produce code containing Year 2000 logic errors. For more details refer to the recommended practices link above. Testing guidelines and recommendations: Since JScript is a programming language, developers should test their individual programs as appropriate for date issues. There are no general concerns common to all JScript programs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Keyboards 1.XX (English)
| - | ||
| None | ||
| MS-DOS 3.1 or higher, Windows 3.1, Windows 95 & all OEM Service Releases, Windows NT 3.51 & all Service Packs | ||
| Operating System Clock | ||
| 30 Sep 1999 | ||
|
This information applies to:
Operational Range for Data: 1853-2107
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Keyboards 1.XX (French)
| - | ||
| None. | ||
| MS-DOS 3.1 or higher, Windows 3.1, Windows 95 & all OEM Service Releases, Windows NT 3.51 & all Service Packs | ||
| Operating System Clock | ||
| 30 Sep 1999 | ||
|
This information applies to:
Operational Range for Data: 1853-2107
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Keyboards 1.XX (German)
| - | ||
| None. | ||
| MS-DOS 3.1 or higher, Windows 3.1, Windows 95 & all OEM Service Releases, Windows NT 3.51 & all Service Packs | ||
| Operating System Clock | ||
| 30 Sep 1999 | ||
|
This information applies to:
Operational Range for Data: 1853-2107
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Keyboards 1.XX (Italian)
| - | ||
| None. | ||
| MS-DOS 3.1 or higher, Windows 3.1, Windows 95 & all OEM Service Releases, Windows NT 3.51 & all Service Packs | ||
| Operating System Clock | ||
| 30 Sep 1999 | ||
|
This information applies to:
Operational Range for Data: 1853-2107
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Keyboards 1.XX (Spanish)
| - | ||
| None. | ||
| MS-DOS 3.1 or higher, Windows 3.1, Windows 95 & all OEM Service Releases, Windows NT 3.51 & all Service Packs | ||
| Operating System Clock | ||
| 30 Sep 1999 | ||
|
This information applies to:
Operational Range for Data: 1853-2107
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
LexiROM 3.0 (German)
| - | ||
| None | ||
| None | ||
| System clock | ||
| 30 Apr 1999 | ||
|
How the product handles dates: LexiROM does not accept user-provided dates for any functionality. Two-digit shortcut handling: LexiROM does not accept user-provided dates for any functionality. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
LexiROM Edition 2000 4.0 (German)
| - | ||
| NONE | ||
| NONE | ||
| System clock | ||
| 18 Oct 1999 | ||
How the product handles dates: LexiROM 4.0 Edition 2000 does not accept user-provided dates. LexiROM 4.0 Edition 2000 does use the system date as input to randomly show different content on startup. Two-digit shortcut handling: LexiROM 4.0 Edition 2000 does not accept user-provided dates. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Link Exchange RTW 01/01/1996 (English)
| 01 Jan 1996 - 31 Dec 2020 | ||
| NONE | ||
| Connection to the InternetBrowser: Internet Explorer 2.x & greater, Netscape 2.x & above, WebTV Classic & Plus, Mac Internet Explorer 2.x & greater | ||
| System Clock | ||
| 04 Oct 1999 | ||
|
How the product handles dates: Dates are used on the Web site for the following:
MSN LinkExchange does not use dates for logic based calculations.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Link Exchange RTW 01/01/1996 (Japanese)
| 01 Jan 1996 - 31 Dec 2020 | ||
| NONE | ||
| Connection to the InternetBrowser: Internet Explorer 2.x & greater, Netscape 2.x & above, WebTV Classic & Plus, Mac Internet Explorer 2.x & greater | ||
| System Clock | ||
| 04 Oct 1999 | ||
|
How the product handles dates: Dates are used on the Web site for the following:
MSN LinkExchange does not use dates for logic based calculations.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Linkage Directory Exchange 3.2 (English)
| 01 Jan 1990 - 31 Dec 2035 | ||
| Software updates as indicated below. | ||
| Microsoft Exchange Server 5.5 with Service Pack 2 or laterMicrosoft SQL Server 6.5 with Service pack 5 or later. | ||
| Not Applicable | ||
| 26 Oct 1999 | ||
|
(Note: LinkAge Directory Exchange (LDE) is not certified for operation on SQL Server 7) How the product handles dates: LinkAge Directory Exchange stores dates internally using 4-digit year values. Calculations and comparisons are done using 4-digit year values. Directory update transactions are transmitted between components of LinkAge Directory Exchange using 4-digit year values. Error messages are written to log files using date/time stamps with 4-digit year values. LinkAge Directory Exchange does not use special values for dates within its operational range. Two-digit shortcut handling: Two-digit shortcuts are not used by the operating components of LDE. However, it is possible to enter 2-digit year values in one of the dialogs of the LDE administration program. See the next section for details. What issues are there?: The LDE administration program, LSADMIN.EXE, generates a message dialog box when using the Directory Exchange Agent (DXA) "Propagation" button when the "Last Update Received", "Last Checked for Updates", "Last Update Sent" and "Last Updates Confirmed" are outside of the year ranging from 1990 to 2015. Directory synchronization proceeds correctly, but the Cancel Button rather than the OK Button must be used to exit the Propagation dialog. The Set Agent Parameters dialog of the LDE administration program does not enforce entry of 4-digit year values. Two-digit year values from 00 to 79 are interpreted as 2000 to 2079. Two-digit year values 80 through 99 are interpreted as 1980 to 1999. Other erroneous year values (such as 3-digit years) can be entered, but will not be properly displayed the next time this dialog box is opened. In general, 4-digit year values should be entered in all dialogs. The Directory Exchange Agent (DXA) for Lotus cc:Mail is not supported after December 31, 1999. This DXA communicates only with non-year 2000-compliant cc:Mail post offices. There are no plans to upgrade this DXA to support compliant cc:Mail post offices. Recommendations to meet compliance: Discontinue use of the DXA for Lotus cc:Mail before December 31, 1999. Enter 4-digit year values in LDE administration dialogs.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Links (English)
| 01 Jan 1900 - 01 Jan 2100 | ||
| None | ||
| Windows 9x, Windows NT | ||
| System Clock | ||
| 11 Nov 1999 | ||
This information applies to: § Links LS 2000 § Links Extreme § Links LS 1999 How the product handles dates: - User does not enter dates. - Date related functions are dependent on the operating system. The product works based on data received from the operating system. Two-digit shortcut handling: The product does not do any date conversion when using two-digit years. Date information is display only and is not critical to the product’s function. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Links 5 Course Library 1.0 (English)
| 01 Jan 1900 - 01 Jan 2100 | ||
| None | ||
| None | ||
| None | ||
| 21 Sep 1999 | ||
|
This information applies to Links 5 Course Library - volumes 1, 2, 3, and 4. How the product handles dates: -User does not enter a date -Date related functions are dependant on the operating system. The product works based on data received from the operating system. Two-digit shortcut handling: None.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Links 5 Course Library 1.0 (English)
| 01 Jan 1900 - 01 Jan 2100 | ||
| None | ||
| None | ||
| None | ||
| 21 Sep 1999 | ||
|
This information applies to Links 5 Course Library - volumes 1, 2, 3, and 4. How the product handles dates: -User does not enter a date -Date related functions are dependant on the operating system. The product works based on data received from the operating system. Two-digit shortcut handling: None.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Liquid Motion 1.0 (English)
| - | ||
| none | ||
| Setup uses InstallFromTheWeb, InstallShield -- pre-release version with TechWave encryption for ESD | ||
| Valid system date is required by setup to complete the installation | ||
| 07 Jul 1999 | ||
| Operational date range: Through 2036 Tool Itself: Dates are not handled in this product. How the product handles dates: Tool Itself: Dates are not handled in this product. Setup: The Electronic Software Distribution setup produced by InstallShield / TechWave installs encryption software, which tracks the number of days since install limiting the trial to 45 days. The credit-card processing component accepts an expiration date in a 2-digit year field. Two-digit shortcut handling: During credit-card transactions, the 2-digits for the year are checked for an exact match. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Magic School Bus (English)
| - | ||||||||||||||||||
| none | ||||||||||||||||||
| Windows 95, Windows 98, Windows NT 4.0, Mac | ||||||||||||||||||
| none | ||||||||||||||||||
| 10 Sep 1999 | ||||||||||||||||||
|
Scholastic's The Magic School Bus Release Date: Aug 1998
Scholastic's The Magic School Bus™ Adventure Series Volumes 1 ships with: Age of Dinosaurs 1.0 Inside the Earth 1.0 Scholastic's The Magic School Bus™ Adventure Series Volumes 2 ships with: Human Body 1.0 Solar System 1.0 Scholastic's The Magic School Bus™ Adventure Series Volumes 3 ships with: Ocean 1.0 Rainforest 1.0
How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
MapPoint 2000 1.0 (English)
| 01 Sep 1998 - 31 Dec 2035 | ||
| None | ||
| Internet Explorer 3.02 or greater, MDAC 2.1 Service Pack 1; HTMLHelp (HHUPD.exe); Answer Wizard; Comctrl32.dll (40Comupd.exe) Windows 95, Windows 98, or Windows NT4 Service Pack 3 or later. | ||
| System Clock | ||
| 27 Oct 1999 | ||
|
Note: If Internet Explorer 3.02 or later is not installed, MapPoint 2000 Setup installs Internet Explorer 5.How the product handles dates: Microsoft MapPoint 2000 handles dates only during installation, when the setup detects the system clock. Two-digit shortcut handling: Not applicable. Recommendations: To check the date in the Pushpin Set properties, which gets its date information from the system clock, do the following:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
MapPoint 2000 1.0 (English British)
| 01 Sep 1998 - 31 Dec 2035 | ||
| None | ||
| Internet Explorer 3.02 or greater, MDAC 2.1 Service Pack 1; HTMLHelp (HHUPD.exe); Answer Wizard; Comctrl32.dll (40Comupd.exe) Windows 95, Windows 98, or Windows NT4 Service Pack 3 or later. | ||
| System Clock | ||
| 03 May 1999 | ||
|
Note: If Internet Explorer 3.02 or later is not installed, MapPoint 2000 Setup installs Internet Explorer 5.How the product handles dates: Microsoft MapPoint 2000 handles dates only during installation, when the setup detects the system clock. Two-digit shortcut handling: Not applicable. Recommendations: To check the date in the Pushpin Set properties, which gets its date information from the system clock, do the following:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
MASM 6.11 (English)
| - | ||
| none | ||
| Operating System(s) on which MASM-developed code is run | ||
| DOS BIOS | ||
| 15 Sep 1999 | ||
|
Microsoft Assembler (MASM) 6.11 Operational Range for Data: to 2035 Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. Note: This requires that any available and appropriate software updates or service packs have been applied. How the product runtime handles dates: @Date macro works just like __DATE__ macro in the Visual C++ Compiler. Two-digit shortcut handling: MASM provides 2-digit shortcuts for display only. Recommended practices to develop year 2000 compliant applications: Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualcDescription of how the product handles dates: Common development errors dealing with year 2000 date issues: The most likely area for concern arises if users write their own date handling routines. Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualcTesting guidelines and recommendations: Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualc
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
MASM 6.13 (English)
| - | ||
| none | ||
| Operating System(s) on which MASM-developed code is run. | ||
| DOS BIOS | ||
| 15 Sep 1999 | ||
|
Microsoft Assembler (MASM) 6.13 Operational Range for Data: to 2035 Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. Note: This requires that any available and appropriate software updates or service packs have been applied. How the product runtime handles dates: @Date macro works just like __DATE__ macro in the Visual C++ compiler. Two-digit shortcut handling: MASM provides 2-digit shortcuts for display only. Recommended practices to develop year 2000 compliant applications: Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualcDescription of how the product handles dates: No intrinsic handling of dates Common development errors dealing with year 2000 date issues: The most likely area for concern arises if users write their own date handling routines. Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualcTesting guidelines and recommendations: Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualc
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Mastering DB Fundmtls - Access 2000 1.0 (English)
| - | ||
| None | ||
| Access 2000 with Typical Wizards and Additional Wizards, Excel 2000, Internet Explorer 4.01 or later, Internet Explorer 5.0 (Lab 7 only) | ||
| Not Applicable | ||
| 03 Nov 1999 | ||
|
Mastering Database Fundamentals Using Microsoft® Access 2000 Overview: Mastering Series courses are an unusual case when evaluated in terms of year 2000 compliance. The viewer application itself contains no date handling functions, but most courses contain lab code, sample applications, small executables and/or references to features in other Microsoft products such as wizards and templates. Therefore, each course has been assessed both from the viewer’s (year 2000) perspective and to ensure that no misleading information (for example, directions to use an external application in a non-compliant manner) or non-compliant code is provided to users. Product Dependencies details: Microsoft Internet Explorer 4.01 or later is needed to execute URL links provided in the product. Microsoft Internet Explorer 5.0 or later is required to complete lab 7. Two-digit shortcut handling: Not Applicable Note: The setup application stores the installation date in the setup.iwf file on the user's hard drive, using 2-digit date format. This date is not entered by the user, and is only displayed when the user reinstalls the product. The date itself is not functionally used by the application. It is for display only. Testing guidelines and recommendations: A code review of storage, display and calculation functions is recommended. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Mastering Distrib. App Design: VS6 1.0 (English)
| - | ||
| None | ||
| Windows NT Server Service Pack 3, Microsoft Visual Studio 6.0 Enterprise Edition (Including: Microsoft Visual Studio 6.0, with MSDN Visual Studio Help, BackOffice, Internet Explorer 4.01, Microsoft Visual J++), Excel 97 | ||
| Not Applicable | ||
| 02 Nov 1999 | ||
|
Mastering Distributed Application Design and Development Using Microsoft® Visual Studio 6® 1.0 Overview: Mastering Series courses are an unusual case when evaluated in terms of year 2000 compliance. The viewer application itself contains no date handling functions, but most courses contain lab code, sample applications, small executables and/or references to features in other Microsoft products such as wizards and templates. Therefore, each course has been assessed both from the viewer’s (year 2000) perspective and to ensure that no misleading information (for example, directions to use an external application in a non-compliant manner) or non-compliant code is provided to users. Product Dependencies details: Microsoft Internet Explorer 4.01 or later is needed to execute URL links provided in the product and to complete labs. Two-digit shortcut handling: Not Applicable What are the issues?: The setup application stores the installation date in the setup.iwf file on the user's hard drive, using 2-digit date format. This date is not entered by the user, and is only displayed when the user reinstalls the product. The date itself is not functionally used by the application. It is for display only. Sample Applications: Food Vendor and Food Vendor Client User Inerface display both two and four-digit year dates, but operates correctly after 1999 .Testing guidelines and recommendations: A code review of storage, display and calculation functions is recommended. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Mastering Ent. Dev VB6 1.0 (English)
| - | ||
| none | ||
| See below | ||
| Not Applicable | ||
| 01 Jun 1999 | ||
|
Mastering Enterprise Development Using Microsoft® Visual Basic® 6 Version: 1.0. Runs on Win NT or 32-Bit Win platforms. Product Dependencies: Microsoft Internet Explorer 3.0 or later; Microsoft Visual Basic 6.0 Enterprise Edition, Microsoft Windows NT4.0 Option Pack, Microsoft SQL Server 6.5, Microsoft SQL Server 6.5 Service Pack 4, Windows NT Server 4.0, Windows NT Server 4.0 Service Pack 3, Island Hopper News Overview: Mastering Series courses are an unusual case when evaluated in terms of year 2000 compliance. The viewer application itself contains no date handling functions, but most courses contain lab code, sample applications, small executables and/or references to features in other Microsoft products such as wizards and templates. Therefore, each course has been assessed both from the viewer’s (year 2000) perspective and to ensure that no misleading information (for example, directions to use an external application in a non-compliant manner) or non-compliant code is provided to users. Product Dependencies details: Microsoft Internet Explorer 3.0 or later is needed to execute URL links provided in the product and to complete labs. Two-digit shortcut handling: Not Applicable What are the issues?: The setup application stores the installation date in the setup.iwf file on the user's hard drive, using 2-digit date format. This date is not entered by the user, and is only displayed when the user reinstalls the product. The date itself is not functionally used by the application. It is for display only. Testing guidelines and recommendations: A code review of storage, display and calculation functions is recommended. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Mastering MFC Dev: VC++6 1.0 (English)
| - | ||
| none | ||
| Microsoft Internet Explorer 3.0 or later; Microsoft Visual C++ 6.0 Professional Edition or Enterprise Edition, Microsoft Personal Web Server | ||
| Not Applicable | ||
| 01 Jun 1999 | ||
|
Mastering MFC Development Using Microsoft® Visual C++® 6 version 1.0. Runs on Win NT and 32-Bit Win platforms. Overview: Mastering Series courses are an unusual case when evaluated in terms of year 2000 compliance. The viewer application itself contains no date handling functions, but most courses contain lab code, sample applications, small executables and/or references to features in other Microsoft products such as wizards and templates. Therefore, each course has been assessed both from the viewer’s (year 2000) perspective and to ensure that no misleading information (for example, directions to use an external application in a non-compliant manner) or non-compliant code is provided to users. Product Dependencies Details: Microsoft Internet Explorer 3.0 or later is needed to execute URL links provided in the product and to complete labs. Two-digit shortcut handling: Not Applicable What are the issues?: The setup application stores the installation date in the setup.iwf file on the user's hard drive, using 2-digit date format. This date is not entered by the user, and is only displayed when the user reinstalls the product. The date itself is not functionally used by the application. It is for display only. Testing guidelines and recommendations: A code review of storage, display and calculation functions is recommended.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Mastering VB6 Dev. 1.0 (English)
| - | ||
| none | ||
| Microsoft Internet Explorer 3.0 or later; Microsoft Visual Basic 6.0 Professional Edition; Microsoft SQL Server 6.5 recommended | ||
| n/a | ||
| 01 Jun 1999 | ||
|
Mastering Microsoft® Visual Basic® 6 Development version: 1.0. Runs on Win NT and 32-Bit Win platforms. Overview: Mastering Series courses are an unusual case when evaluated in terms of year 2000 compliance. The viewer application itself contains no date handling functions, but most courses contain lab code, sample applications, small executables and/or references to features in other Microsoft products such as wizards and templates. Therefore, each course has been assessed both from viewer’s (year 2000) perspective and to ensure that no misleading information (for example, directions to use an external application in a non-compliant manner) or non-compliant code is provided to users. Product Dependencies details: Microsoft Internet Explorer 3.0 or later is needed to execute URL links provided in the product and to complete labs Two-digit shortcut handling: Not Applicable What are the issues?: The setup application stores the installation date in the setup.iwf file on the user's hard drive, using 2-digit date format. This date is not entered by the user, and is only displayed when the user reinstalls the product. The date itself is not functionally used by the application. It is for display only. Testing guidelines and recommendations: A code review of storage, display and calculation functions is recommended.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Mastering VB6 Fundamentals 1.0 (English)
| - | ||
| none | ||
| Microsoft Internet Explorer 4.01 Service Pack 1 or later; Microsoft Visual Basic 6.0 Professional Edition | ||
| Not Applicable | ||
| 01 Jun 1999 | ||
|
Mastering Microsoft® Visual Basic® 6 Fundamentals version 1.0. Runs on Win NT and 32-Bit Win platforms. Overview: Mastering Series courses are an unusual case when evaluated in terms of year 2000 compliance. The viewer application itself contains no date handling functions, but most courses contain lab code, sample applications, small executables and/or references to features in other Microsoft products such as wizards and templates. Therefore, each course has been assessed both from the viewer’s (year 2000) perspective and to ensure that no misleading information (for example, directions to use an external application in a non-compliant manner) or non-compliant code is provided to users. Product Dependencies details: Microsoft Internet Explorer 4.01 Service Pack 1 or later is needed to execute URL links provided in the product and to complete labs. Two-digit shortcut handling: Not Applicable What are the issues? The setup application stores the installation date in the setup.iwf file on the user's hard drive, using 2-digit date format. This date is not entered by the user, and is only displayed when the user reinstalls the product. The date itself is not functionally used by the application. It is for display only.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Mastering Web App Dev: Vis Interdev 1.0 (English)
| - | ||
| none | ||
| See below | ||
| Not Applicable | ||
| 01 Jun 1999 | ||
|
Mastering Web Application Development Using Visual Interdev™ 6 version 1.0. Runs on Win NT and 32-Bit Win platforms. Product Dependencies: Microsoft Internet Explorer 3.0 or later; Microsoft Personal Web Server, Microsoft Windows NT 4.0 Option Pack, Microsoft Internet Explorer 4.01 Service Pack 1a, Microsoft Visual Interdev 6.0 Professional Edition, Microsoft Visual Basic 6.0 Professional Edition, Microsoft SQL Server 6.5 or Microsoft Access 97 Overview: Mastering Series courses are an unusual case when evaluated in terms of year 2000 compliance. The viewer application itself contains no date handling functions, but most courses contain lab code, sample applications, small executables and/or references to features in other Microsoft products such as wizards and templates. Therefore, each course has been assessed both from the viewer’s (year 2000) perspective and to ensure that no misleading information (for example, directions to use an external application in a non-compliant manner) or non-compliant code is provided to users. Product Dependencies details: Microsoft Internet Explorer 3.0 or later is needed to execute URL links provided in the product and for the labs Two-digit shortcut handling: Not Applicable. What are the issues?: The setup application stores the installation date in the setup.iwf file on the user's hard drive, using 2-digit date format. This date is not entered by the user, and is only displayed when the user reinstalls the product. The date itself is not functionally used by the application. It is for display only.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Message Queue Service (English)
| - | ||
| Windows NT 4.0 SP4 | ||
| 26 Aug 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4, sp4 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft C 5.1 (English)
| 01 Jan 1980 - 18 Jan 2038 | ||||||||
| None | ||||||||
| MSDOS 6.22 and OS/2 1.3 | ||||||||
| System Clock | ||||||||
| 15 Sep 1999 | ||||||||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. Note: This requires that any available and appropriate software updates have been applied. How the product runtime handles dates: Microsoft C 5.10 uses the following data types for dates:
Two-digit shortcut handling: Two-digit dates are display only; there is no input of 2-digit dates in the product. Recommended practices to develop year 2000 compliant applications: Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualc. How the product handles dates: Common development errors dealing with year 2000 date issues: The most likely area for concern arises if users write their own date handling routines. Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualc. The Microsoft C Run Time provides two ANSI-C data structures to track time. These are:
ANSI types: struct tm and time_t The ANSI C standard has established these types, their meaning and to some extent, the underlying type of each. In Visual C++, the type of time_t is long and it represents seconds since January 1, 1970 when used with the ANSI C functions that utilize variables of this type. The type struct tm is used to track the components of a date. The struct tm uses internal variables to store years as the number of years since 1900, the month of the year, day of the week, day of the month, day of the year, hour of the day, minute of the hour, and seconds of the minute are accounted for in this structure as well as if Daylight Savings Time is in effect. These members are of type int. These types are what ANSI functions use to manipulate, input, and output times. The Visual C++ documentation has more information on these types. Avoiding issues with ANSI time functions An application can appear to have a year 2000 issue because of how ANSI functions are permitted to behave. You can create year 2000 compliant applications and avoid confusing output from your programs if you follow some simple guidelines when using ANSI functions, primarily the strftime and wcsftime functions.
#include <time.h> #include <stdio.h> const int BUFSIZE = 1024; char buf[BUFSIZE]; int main() { struct tm now; time_t tmp = time(0); // current time now = *localtime(&tmp); size_t len = strftime(buf, BUFSIZE, "%#c\n", &now); now.tm_hour += 48; //jump ahead two days // should get a bogus hour value len += strftime(buf+len, BUFSIZE-len, "%#c\n", &now); mktime(&now); // mktime will correct strftime(buf+len, BUFSIZE-len, "%#c\n", &now); printf(buf); return 0; } Although not an ANSI function, the _strdate and _wstrdate functions generates a 9-character string to a buffer that it receives a pointer to as a parameter. The output has the form "MM/DD/YY". Use the strftime or wcsftime function instead. Testing guidelines and recommendations: Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualc
| ||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft C 6.00a (English)
| 01 Jan 1980 - 18 Jan 2038 | ||||||||
| None | ||||||||
| MSDOS 6.22 and OS/2 1.3 | ||||||||
| System Clock | ||||||||
| 10 Sep 1999 | ||||||||
|
Can applications be built with this tool that adhere to the Microsoft Year 2000 Compliance Statement? Yes. Note: This requires that any available and appropriate software updates have been applied. How the product runtime handles dates: Microsoft C 6.00a uses the following data types for dates:
Two-digit shortcut handling: Two-digit dates are display only; there is no input of 2-digit days in the product. Recommended practices to develop year 2000 compliant applications: Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualc How the product handles dates: No intrinsic handling of dates. Common development errors dealing with year 2000 date issues: The most likely area for concern arises if users write their own date handling routines. Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualc. The Microsoft C Run Time provides two ANSI-C data structures to track time. These are
ANSI types: struct tm and time_t The ANSI C standard has established these types, their meaning and to some extent, the underlying type of each. In Visual C++, the type of time_t is long and it represents seconds since January 1, 1970 when used with the ANSI C functions that utilize variables of this type. The type struct tm is used to track the components of a date. The struct tm uses internal variables to store years as the number of years since 1900, the month of the year, day of the week, day of the month, day of the year, hour of the day, minute of the hour, and seconds of the minute are accounted for in this structure as well as if Daylight Savings Time is in effect. These members are of type int. These types are what ANSI functions use to manipulate, input, and output times. The Visual C++ documentation has more information on these types. Avoiding issues with ANSI time functions An application can appear to have a year 2000 issue because of how ANSI functions are permitted to behave. You can create year 2000 compliant applications and avoid confusing output from your programs if you follow some simple guidelines when using ANSI functions, primarily the strftime and wcsftime functions.
#include <time.h> #include <stdio.h> const int BUFSIZE = 1024; char buf[BUFSIZE]; int main() { struct tm now; time_t tmp = time(0); // current time now = *localtime(&tmp); size_t len = strftime(buf, BUFSIZE, "%#c\n", &now); now.tm_hour += 48; //jump ahead two days // should get a bogus hour value len += strftime(buf+len, BUFSIZE-len, "%#c\n", &now); mktime(&now); // mktime will correct strftime(buf+len, BUFSIZE-len, "%#c\n", &now); printf(buf); return 0; } Although not an ANSI function, the _strdate and _wstrdate functions generates a 9-character string to a buffer that it receives a pointer to as a parameter. The output has the form "MM/DD/YY". Use the strftime or wcsftime function instead. Testing guidelines and recommendations: Please see the "Visual C++ and the Year 2000" best practices article located at http://www.msdn.microsoft.com/visualc
| ||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Arabic)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Chinese - Simplified)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Chinese - Traditional)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Czech)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Dutch)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (English)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (French)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (German)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Hebrew)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Italian)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Japanese)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Korean)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Norwegian)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Portuguese (Brazil))
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Spanish)
| - | ||
| Windows NT 4.0 Service Pack 4, Service Pack 5, or Service Pack 6 | ||
| 05 Oct 1999 | ||
|
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4.0 Server SP4, SP5, and SP6 compliance document. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Itemized List of products in each Volume
|
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://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.
|
||
|
Wednesday, November 17, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act.  | ||