Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Microsoft Clustering Service (Swedish)
| - | ||
| 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 (Thai)
| - | ||
| 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 Host Data Replicator 1.0 (English)
| - | ||
| none | ||
| Windows NT 3.51 Service Pack 5, and SNA Server 3.0 Service Pack 3 | ||
| See below | ||
| 15 Jan 1999 | ||
|
Clock Dependencies: System Clock,mktime( ) asctime( ) ctime( ) FileTimeToSystemTime( ) GetLocalTime( ) GetSystemTime( ) gmtime( ) localtime( ) mktime( ) SystemTimeToFileTime( ) time( ) Notes to Users: Host Data Replicator 1.0 is no longer a Microsoft product. StarQuest Inc. has taken sole ownership of this product. Please contact StarQuest for Year 2000 compliance issues. StarQuest: Main phone number: 510-704-2000 WEB home page: http://starweb.starware.com/Email address: support@starquest.com | ||
| 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 Host Data Replicator 1.0 (Japanese)
| - | ||
| none | ||
| Windows NT 3.51 Service Pack 5, and SNA Server 3.0 Service Pack 3 | ||
| see below | ||
| 09 Apr 1999 | ||
|
Clock Dependencies: System Clock,mktime( ) asctime( ) ctime( ) FileTimeToSystemTime( ) GetLocalTime( ) GetSystemTime( ) gmtime( ) localtime( ) mktime( ) SystemTimeToFileTime( ) time( ) Notes to Users: Host Data Replicator 1.0 is no longer a Microsoft product. StarQuest Inc. has taken sole ownership of this product. Please contact StarQuest for Year 2000 compliance issues. StarQuest: Main phone number: 510-704-2000 WEB home page: http://starweb.starware.com/Email address: support@starquest.com | ||
| 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 Mail for PC Networks 3.5 (Danish)
| 01 Jan 1970 - 31 Dec 2035 | ||
| Year 2000 product software updates identified below | ||
| Windows NT 3.51, MS-DOS 6.22 | ||
| Windows NT System clock, PC BIOS | ||
| 27 Oct 1999 | ||
|
This document is applicable to Microsoft Mail for PC Networks components, Win Mail Client 3.5, Remote Mail Client 3.2. ** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 – December 31, 2019. This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Danish versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks. Some of the issues and what was tested with the Danish client accessing the English Microsoft Mail Post Office are covered in this document. Updates for the English server components are also needed. What are the prerequisites?
To resolve known issues with Microsoft Mail 3.5 Danish components, software updates need to be applied to: Windows Remote Mail Client 3.2. These component software update is only required if the component is used by the customer. For instance, if the customer’s mail environment does not include the Windows Remote Mail Client then this specific software update would not be needed. This is a list of the components and their executable names that have product software updates: Microsoft Mail Windows Remote 3.2 client: Windows Remote client REMCY2K.EXE The set of instructions for installing the Microsoft Mail client and server components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/dan/all-y2k/Readmeus.txtThe following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components. Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp?SPR=
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
What was not tested with Microsoft Mail 3.5? Two-digit shortcut handling: There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits. Does 2-digit shortcut handling workaround everything? No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018. Common date usage errors: Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendors’ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any two-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5. Testing guidelines and recommendations: Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | ||
| 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 Mail for PC Networks 3.5 (English)
| 01 Jan 1970 - 31 Dec 2035 | ||
| Year 2000 product fixes identified below | ||
| Windows NT 3.51, MS-DOS 6.22 | ||
| Windows NT System clock, PC BIOS | ||
| 27 Oct 1999 | ||
|
This document is applicable to Microsoft Mail for PC Networks components, Win Mail Client 3.5, Remote Mail Client 3.2. ** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 – December 31, 2019. This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Danish versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks. Some of the issues and what was tested with the Danish client accessing the English Microsoft Mail Post Office are covered in this document. Updates for the English server components are also needed. What are the prerequisites?
To resolve known issues with Microsoft Mail 3.5 Danish components, software updates need to be applied to: Windows Remote Mail Client 3.2. These component software update is only required if the component is used by the customer. For instance, if the customer’s mail environment does not include the Windows Remote Mail Client then this specific software update would not be needed. This is a list of the components and their executable names that have product software updates: Microsoft Mail Windows Remote 3.2 client: Windows Remote client REMCY2K.EXE The set of instructions for installing the Microsoft Mail client and server components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/dan/all-y2k/Readmeus.txtThe following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components. Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp?SPR=
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
What was not tested with Microsoft Mail 3.5? Two-digit shortcut handling: There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits. Does 2-digit shortcut handling workaround everything? No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018. Common date usage errors: Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendors’ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any two-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5. Testing guidelines and recommendations: Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | ||
| 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 Mail for PC Networks 3.5 (Finnish)
| 01 Jan 1970 - 31 Dec 2035 | ||
| Year 2000 product software updates identified below | ||
| Windows NT 3.51, MS-DOS 6.22 | ||
| Windows NT System clock, PC BIOS | ||
| 27 Oct 1999 | ||
|
This document is applicable to Microsoft Mail for PC Networks components, Win Mail Client 3.5, Remote Mail Client 3.2. ** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 – December 31, 2019. This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Danish versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks. Some of the issues and what was tested with the Danish client accessing the English Microsoft Mail Post Office are covered in this document. Updates for the English server components are also needed. What are the prerequisites?
To resolve known issues with Microsoft Mail 3.5 Danish components, software updates need to be applied to: Windows Remote Mail Client 3.2. These component software update is only required if the component is used by the customer. For instance, if the customer’s mail environment does not include the Windows Remote Mail Client then this specific software update would not be needed. This is a list of the components and their executable names that have product software updates: Microsoft Mail Windows Remote 3.2 client: Windows Remote client REMCY2K.EXE The set of instructions for installing the Microsoft Mail client and server components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/dan/all-y2k/Readmeus.txtThe following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components. Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp?SPR=
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
What was not tested with Microsoft Mail 3.5? Two-digit shortcut handling: There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits. Does 2-digit shortcut handling workaround everything? No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018. Common date usage errors: Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendors’ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any two-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5. Testing guidelines and recommendations: Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | ||
| 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 Mail for PC Networks 3.5 (French)
| 01 Jan 1970 - 31 Dec 2035 | ||
| Year 2000 product software updates identified below | ||
| Windows NT 3.51, MS-DOS 6.22 | ||
| Windows NT System clock, PC BIOS | ||
| 27 Oct 1999 | ||
|
This document is applicable to Microsoft Mail for PC Networks components, Win Mail Client 3.5, Remote Mail Client 3.2. ** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 – December 31, 2019. This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Danish versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks. Some of the issues and what was tested with the Danish client accessing the English Microsoft Mail Post Office are covered in this document. Updates for the English server components are also needed. What are the prerequisites?
To resolve known issues with Microsoft Mail 3.5 Danish components, software updates need to be applied to: Windows Remote Mail Client 3.2. These component software update is only required if the component is used by the customer. For instance, if the customer’s mail environment does not include the Windows Remote Mail Client then this specific software update would not be needed. This is a list of the components and their executable names that have product software updates: Microsoft Mail Windows Remote 3.2 client: Windows Remote client REMCY2K.EXE The set of instructions for installing the Microsoft Mail client and server components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/dan/all-y2k/Readmeus.txtThe following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components. Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp?SPR=
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
What was not tested with Microsoft Mail 3.5? Two-digit shortcut handling: There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits. Does 2-digit shortcut handling workaround everything? No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018. Common date usage errors: Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendors’ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any two-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5. Testing guidelines and recommendations: Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | ||
| 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 Mail for PC Networks 3.5 (German)
| 01 Jan 1970 - 31 Dec 2035 | ||
| Year 2000 product software updates identified below | ||
| Windows NT 3.51, MS-DOS 6.22 | ||
| Windows NT System clock, PC BIOS | ||
| 27 Oct 1999 | ||
|
This document is applicable to Microsoft Mail for PC Networks components, Win Mail Client 3.5, Remote Mail Client 3.2. ** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 – December 31, 2019. This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Danish versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks. Some of the issues and what was tested with the Danish client accessing the English Microsoft Mail Post Office are covered in this document. Updates for the English server components are also needed. What are the prerequisites?
To resolve known issues with Microsoft Mail 3.5 Danish components, software updates need to be applied to: Windows Remote Mail Client 3.2. These component software update is only required if the component is used by the customer. For instance, if the customer’s mail environment does not include the Windows Remote Mail Client then this specific software update would not be needed. This is a list of the components and their executable names that have product software updates: Microsoft Mail Windows Remote 3.2 client: Windows Remote client REMCY2K.EXE The set of instructions for installing the Microsoft Mail client and server components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/dan/all-y2k/Readmeus.txtThe following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components. Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp?SPR=
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
What was not tested with Microsoft Mail 3.5? Two-digit shortcut handling: There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits. Does 2-digit shortcut handling workaround everything? No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018. Common date usage errors: Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendors’ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any two-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5. Testing guidelines and recommendations: Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | ||
| 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 Mail for PC Networks 3.5 (Italian)
| 01 Jan 1970 - 31 Dec 2035 | ||
| Year 2000 product software updates identified below | ||
| Windows NT 3.51, MS-DOS 6.22 | ||
| Windows NT System clock, PC BIOS | ||
| 27 Oct 1999 | ||
|
This document is applicable to Microsoft Mail for PC Networks components, Win Mail Client 3.5, Remote Mail Client 3.2. ** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 – December 31, 2019. This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Danish versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks. Some of the issues and what was tested with the Danish client accessing the English Microsoft Mail Post Office are covered in this document. Updates for the English server components are also needed. What are the prerequisites?
To resolve known issues with Microsoft Mail 3.5 Danish components, software updates need to be applied to: Windows Remote Mail Client 3.2. These component software update is only required if the component is used by the customer. For instance, if the customer’s mail environment does not include the Windows Remote Mail Client then this specific software update would not be needed. This is a list of the components and their executable names that have product software updates: Microsoft Mail Windows Remote 3.2 client: Windows Remote client REMCY2K.EXE The set of instructions for installing the Microsoft Mail client and server components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/dan/all-y2k/Readmeus.txtThe following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components. Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp?SPR=
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
What was not tested with Microsoft Mail 3.5? Two-digit shortcut handling: There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits. Does 2-digit shortcut handling workaround everything? No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018. Common date usage errors: Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendors’ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any two-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5. Testing guidelines and recommendations: Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | ||
| 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 Mail for PC Networks 3.5 (Japanese)
| 01 Jan 1970 - 31 Dec 2035 | ||
| Year 2000 product software updates identified below | ||
| Windows NT 3.51, MS-DOS 6.2 | ||
| Windows NT System clock, PC BIOS | ||
| 27 Oct 1999 | ||
|
This document is applicable to Microsoft Mail for PC Networks components, FAX Gateway 3.0, Win Mail Client 3.5. ** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 – December 31, 2019. This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Japanese versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks. What are the prerequisites?
To resolve known issues with Microsoft Mail 3.5, software updates need to be applied in two main areas: 1. Microsoft Mail 3.5 server, 2. FAX Gateway 3.0. These component software updates are only required if the component is used by the customer. For instance, if the customer’s mail environment does not have a FAX gateway installed then this specific software update would not be needed. This is a list of the components and their executable names that have product software updates: Microsoft Mail 3.5 components: Administrator program ADMY2K.EXE Directory Synchronization components DIRSY2K.EXE External program EXTY2K.EXE FAX Gateway component: FAX gateway FAXGY2K.EXE The set of instructions for installing the Microsoft Mail server and gateway components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/jpn/all-y2k/readme.txtThe following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components. Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp?SPR=
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
What was not tested with Microsoft Mail 3.5? Two-digit shortcut handling: There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits. Does 2-digit shortcut handling workaround everything? No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018. Common date usage errors: Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendors’ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any 2-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5. Testing guidelines and recommendations: Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | ||
| 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 Mail for PC Networks 3.5 (Spanish)
| 01 Jan 1970 - 31 Dec 2035 | ||
| Year 2000 product software updates identified below | ||
| Windows NT 3.51, MS-DOS 6.22 | ||
| Windows NT System clock, PC BIOS | ||
| 27 Oct 1999 | ||
|
This document is applicable to Microsoft Mail for PC Networks components, Win Mail Client 3.5, Remote Mail Client 3.2. ** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 – December 31, 2019. This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Spanish versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks. Some of the issues and what was tested with the Spanish client accessing the English Microsoft Mail Post Office are covered in this document. Updates for the English server components are also needed. What are the prerequisites?
To resolve known issues with Microsoft Mail 3.5 Spanish components, software updates need to be applied to: Windows Remote Mail Client 3.2. These component software update is only required if the component is used by the customer. For instance, if the customer’s mail environment does not include the Windows Remote Mail Client then this specific software update would not be needed. This is a list of the components and their executable names that have product software updates: Microsoft Mail Windows Remote 3.2 client: Windows Remote client REMCY2K.EXE The set of instructions for installing the Microsoft Mail client and server components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/spa/all-y2k/Readmeus.txtThe following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components. Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp?SPR=
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
What was not tested with Microsoft Mail 3.5? Two-digit shortcut handling: There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits. Does 2-digit shortcut handling workaround everything? No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018. Common date usage errors: Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendors’ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any two-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5. Testing guidelines and recommendations: Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | ||
| 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 Mail for PC Networks 3.5 (Swedish)
| 01 Jan 1970 - 31 Dec 2035 | ||
| Year 2000 product software updates identified below | ||
| Windows NT 3.51, MS-DOS 6.22 | ||
| Windows NT System clock, PC BIOS | ||
| 27 Oct 1999 | ||
|
This document is applicable to Microsoft Mail for PC Networks components, Win Mail Client 3.5, Remote Mail Client 3.2. ** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 – December 31, 2019. This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Swedish versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks. What are the prerequisites?
To resolve known issues with Microsoft Mail 3.5, software updates need to be applied in two main areas: 1. Microsoft Mail 3.5 server, 2. Windows Remote Mail Client 3.2 These component software updates are only required if the component is used by the customer. For instance, if the customer’s mail environment does not include the Windows Remote Mail Client then this specific software update would not be needed. This is a list of the components and their executable names that have product software updates: Microsoft Mail 3.5 components: Administrator program ADMY2K.EXE Directory Synchronization components DIRSY2K.EXE External program EXTY2K.EXE Microsoft Mail Windows Remote 3.2 client: Windows Remote client REMCY2K.EXE The set of instructions for installing the Microsoft Mail client and server components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/swe/all-y2k/Readmeus.txtThe following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components. Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp?SPR=
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
What was not tested with Microsoft Mail 3.5? Two-digit shortcut handling: There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits. Does 2-digit shortcut handling workaround everything? No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018. Common date usage errors: Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendors’ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any 2-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5. Testing guidelines and recommendations: Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | ||
| 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 Official Curriculum (MOC) (English)
| - | ||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.xx, Exchange Server 5.5, SQL Server 7.0, Systems Management Server 2.0, Windows NT Server 4.0 Enterprise Edition, Proxy Server 2.0, Windows NT Server 4.0 Terminal Server Edition | ||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||
|
Microsoft Official Curriculum (MOC) courseware developed for Microsoft Windows NT 4.xx and Microsoft BackOffice products has been tested and there are no known issues. The curriculum is offered at Microsoft Certified Technical Education Centers (CTEC). How the product handles dates: This product does not handle dates or perform 2-digit year shortcut interpretations.
| ||||||||||||||||||||||||||||||||||||||||||||
| 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 OLE DB 1.5 (Chinese - Simplified)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Chinese - Traditional)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Czech)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Danish)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Dutch)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (English)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Finnish)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (French)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (German)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Greek)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Hungarian)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Italian)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Japanese)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Korean)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Norwegian)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Polish)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Portuguese (Brazil))
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Portuguese)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Russian)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Slovak)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Slovenian)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Spanish)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Swedish)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 1.5 (Turkish)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 1.5 as originally released is Compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s Compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is Compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 2.0 (Chinese - Simplified)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 2.0 as originally released is compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 2.0 (Chinese - Traditional)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 2.0 as originally released is compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 2.0 (English)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 2.0 as originally released is compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 2.0 (French)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 2.0 as originally released is compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 2.0 (German)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 2.0 as originally released is compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 2.0 (Italian)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 2.0 as originally released is compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 2.0 (Japanese)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 2.0 as originally released is compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 2.0 (Korean)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 2.0 as originally released is compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 OLE DB 2.0 (Spanish)
| - | ||
| Windows NT4 Service Pack 4 or higher, or Windows 9x operating systems | ||
| OLEAUT32, COM, msvcrt.dll, | ||
| None except that datetime data will always correspond to the data source. | ||
| 11 Nov 1999 | ||
|
OLE DB 2.0 as originally released is compliant#. A description of the issues is given below. Updated versions of OLE DB (with the correction bringing it to full compliance) are being made available through Microsoft Data Access Components (MDAC) 2.0 Service Pack 1, which shipped with Windows NT4 Service Pack 4 Microsoft Data Access Components (MDAC) 2.1 See Note 2 below for more information. How the product handles dates: The five OLE DB data types that store date-time information are DBTYPE_DATE, DBTYPE_DBTIME, DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_FILETIME. Of these, DBTYPE_DBTIME does not store date information. The other four data types store the date information compatible with a longhand 4-year digit convention. Therefore, the date issues are the conversions involving strings. DBTYPE_DBTIMESTAMP, DBTYPE_DBDATE, and DBTYPE_DBTIMESTAMP string conversions are based on ISO. However, they will also accept OLE Automation date formats, including dates with 2-digit year shortcuts. Two-digit shortcut handling: OLE DB uses the standard OLEAUT solution that interprets 00-29 as 20XX and 30-99 as 19XX. Common date usage errors: Always use 4-digit year when storing data or calling methods/properties of any of the MDAC data access APIs. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the date features of most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. Known issues: The known Year 2000 issues for OLE DB data coercion library are: If you code to ADO, AND your ADO Recordset includes Date data types, such as: adDate, adDBDate, adFileTime, or adDBTimeStamp. AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1t, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am). OR, If you code directly to OLE DB, the same case exists: If you're converting from a variant (BSTR, VARIANT or PROPVARIANT) to date datatypes, such as: DBTYPE_DATE DBTYPE_DBDATE DBTYPE_DBTIME DBTYPE_FILETIME DBTYPE_DBTIMESTAMP AND you're using a date format in which periods are used instead of slashes for date separator (01.01.98 instead of 01/01/98) AND you specify a year less than 60, THEN Data Convert (msdadc.dll) may translate your date as a time. For example, 01.01.01 (January 1, 2001) could be converted to 01:01:01 (December 30, 1899, 1:01:01am).
NOTE 1: If you're coding directly to OLE DB, and you’re converting a Variant BSTR to DBDATE, the date "0001-01-01" may be interpreted as "2001-01-01". This issue only affects the years 0001 to 0099. For this reason, the operational range should be considered to start no lower than year 0100. NOTE 2: To distinguish a compliant version of OLE DB from one that’s compliant#: 1) check the version of the DLL pointed to by this registry key: HKEY_CLASSES_ROOT\CLSID\{c8b522d1-5cf3-11ce-ade5-00aa0044773d}\InprocServer32\(default) 2) OLE DB is compliant# if the version is greater than 1.50.0000 and less than 1.50.9801, or greater than 2.0.0000.00 and less than 2.0.3002.23, OLE DB is compliant if the version is greater than or equal to 1.50.9801 and less than 2.0.0000.00, or greater than or equal to 2.0.3002.23, or greater than or equal to 2.10.0000.00
| ||
| 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 Plus! 95 1.0 (Chinese - Traditional)
| - | ||
| None | ||
| None | ||
| None | ||
| 17 Feb 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (Danish)
| - | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (Dutch)
| - | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (English)
| - | ||
| NONE | ||
| NONE | ||
| NONE | ||
| 17 Feb 1999 | ||
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: | ||
| 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 Plus! 95 1.0 (Finnish)
| - | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (French)
| - | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (German)
| - | ||
| None | ||
| None | ||
| None | ||
| 17 Feb 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (Italian)
| - | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (Japanese)
| - | ||
| None | ||
| None | ||
| None | ||
| 17 Feb 1999 | ||
|
This document applies to both Japanese and Japanese (PC98). How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (Korean)
| - | ||
| None | ||
| None | ||
| None | ||
| 17 Feb 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (Norwegian)
| - | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (Portuguese (Brazil))
| - | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (Spanish)
| - | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 95 1.0 (Swedish)
| - | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
How the product handles dates: Plus! 95 is aware of dates beyond the year 2000 and components that store dates do so using all 4 digits for the year. Some components that display the date do not use all four digits but date calculations use 4 digit years. Two-digit shortcut handling: System Agent does not accept 2-digit shortcuts for any year. Dates must be entered using all four digits for the year. If a 2-digit year is entered, System Agent automatically changes the year to 1980. Product compliance issues: In some areas, System Agent does not display dates using 4 digits for the year. System Agent does not accept a 2-digit shortcut for any year. When entering a date, the year must be specified using all 4 digits. The version of Internet Explorer that ships in Plus! 95 has not been tested for Year 2000 compliance. To ensure compliance please ensure that you upgrade to Microsoft Internet Explorer 4.01 with Service Pack 1. | ||
| 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 Plus! 98 (English)
| 01 Jan 1980 - 31 Dec 2035 | ||||
| None | ||||
| None | ||||
| None | ||||
| 11 Mar 1999 | ||||
|
| ||||
| 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 Plus! 98 (French)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
Product Details
| ||
| 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 Plus! 98 (German)
| 01 Jan 1980 - 31 Dec 2035 | ||||
| None | ||||
| None | ||||
| None | ||||
| 03 Aug 1999 | ||||
| ||||
| 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 Plus! 98 (Italian)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
Product Details
| ||
| 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 Plus! 98 (Japanese)
| 01 Jan 1980 - 31 Dec 2035 | ||||
| None | ||||
| None | ||||
| None | ||||
| 12 Jul 1999 | ||||
| ||||
| 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 Plus! 98 (Spanish)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| None | ||
| None | ||
| 24 Mar 1999 | ||
|
Product Details
| ||
| 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 Virtual Machine (Chinese - Simplified)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3;Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Chinese - Traditional)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3;Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Czech)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3;Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Danish)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Dutch)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (English)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Finnish)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (French)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (German)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Greek)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Hungarian)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Italian)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Japanese)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Korean)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Norwegian)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Polish)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Portuguese (Brazil))
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Portuguese)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Russian)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Slovak)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Slovenian)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Spanish)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Swedish)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3; Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 Virtual Machine (Turkish)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Updated Microsoft VM version 1520 or later (applies to the VM 15xx series only), Updated Microsoft VM version 2436 or later (applies to the VM 24xx series only), Updated Microsoft VM version 3165 or later (applies to the VM 3xxx series only). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT Service Pack 3;Internet Explorer 3.02 with Microsoft VM 15xx; Internet Explorer 4.01 with Microsoft VM 24xx or Microsoft VM 3xxx; Internet Explorer 5.0 with Microsoft VM 3xxx | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Nov 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There are many versions of the Microsoft Virtual Machine (VM) that are available or in use today. Updated versions are made available relatively frequently. This document is designed to explain the year 2000 status for the various version of the Microsoft VM along with recommendations regarding known Year 2000 issues.
How can users determine what version of the Microsoft VM they are using? Users should first determine what version of the Microsoft VM they are running.
Or
Released versions of the Microsoft Virtual Machine are listed below. Known year 2000 issues related to each VM are included as well as the recommended upgrade path to fix such issues.
* This is the same Microsoft VM as 2424. "2405" is displayed when Jview is typed at the command prompt. Section 1 Microsoft VM Versions: 1158–1518 are ""Not Compliant" Description of how the product handles dates: With this series of the VM, version 1158–1518, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). The valid range of dates for these VMs, based on Java 1.02, is 1970 to 2037. Any date outside of that range is returned as being out of range. The java.util.date class is the built-in date manipulation and storage class for Java 1.02. This class provides a number of methods for manipulating, storing and converting dates. Two-digit shortcut handling: VMs 1158–1518 handles the 2-digit year shortcut by adding the given year to 1900 to produce the 4-digit year. Date Handling Issues: The hundred-year sliding date window is not implemented in VMs 1158-1518. This limits the range of years with the two-digit shortcut to 1970-1999. The sliding date window is implemented in VM 1520. Example: Attempting to parse the date 4/12/02 would result in a java.lang.illegalArgumentException. Recommendations: Upgrade to Microsoft VM version 1520 (or a later 15xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm.
Microsoft VM Version: 1520 (or later 15xx series VM) is "Compliant." Issues addressed by 1520: VM 1520 handles dates the same as 1158-1518, with the exception of the 2-digit year shortcut format. With 1520 an "80/20" hundred-year sliding date window is used to "place" the date in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Section 2 Microsoft VM Version: 2057–2339 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2057-2339, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range with 4-digit years. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: VMs 2057-2339 handle the 2-digit year shortcut by adding the year given to 1900 to produce the 4-digit year. Date Handling Issues: Issue 1: The sliding window is not implemented with these VMs. Using 2-digit years and the java.text.SimpleDateFormat parser, the date range is 1900-1999. Example 1: Attempting to parse the date 4/12/02 with the 1.02 java.util.date would result in a java.lang.illegalArgumentException. Example 2: Attempting to parse the date 4/12/02 into a 4-digit year with the 1.1 java.text.SimpleDateFormat class would result in 4/12/1902. Issue 2: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/1916. The parser sees the 16 and adds it to 1900 to create the 4-digit date. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and adds it to 1900 to create the 4-digit date. Issue 3: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2424 is "Not Compliant." Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs parses 4-digit years with the Java 1.1 date classes by using the first 2 digits. Example 1: Entering the date 2/3/1678 would parse to 2/3/2016. The parser sees the 16 and it falls into the upper portion of the sliding window, so it maps to the 2000s. Example 2: Entering the date 5/12/2020 would parse to 5/12/1920. The parser sees the 20 and it falls into the lower portion of the sliding window, so it maps to the 1900s. Issue 2: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2424: The 80/20 sliding window is now implemented for both the Java 1.02 java.util.date class and the java 1.1 java.text.SimpleDateFormat parser. The java.util.date class does not have any known issues with respect to parsing 4-digit dates. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2435 is "Not Compliant". Description of how the product handles dates: With this VM, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the two-digit year in the "correct" century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Issues Addressed in VM 2435: This includes the fixes in 2424 and has no known issues reading 4-digit years with the java.text.SimpleDateFormat parser. Recommendations: Upgrade to Microsoft VM version 2436 (or a later 24xx series VM) available from http://www.microsoft.com/java/vm/dl_vmsp2.htm or version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 2436 (or later 24xx series VM) is "Compliant". Issues addressed by 2436: This VM includes the fixes in 2424 and 2435 and resolves the 2/29/00 parser issue.
Section 3 Microsoft VM Version: 2613 is "Not Compliant". Issues: This VM has the same date handling issues as VMs 2057–2339. See that section above for details. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.Microsoft VM Version: 2750–3161 are "Not Compliant." Description of how the product handles dates: With this series of the VM, version 2750–3161, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This series of VMs includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: These VMs handle the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Date Handling Issues: Issue 1: The java.text.SimpleDateFormat parser included in these VMs does not recognize the date 2/29/00. This date will return a java.lang.IllegalArgumentException. Recommendations: Upgrade to Microsoft VM version 3167 (or a later 3xxx series VM) available from http://www.microsoft.com/java/vm/dl_vm32.htm.
Microsoft VM Version: 3165 (or later 3xxx series VM) is "Compliant."Description of how the product handles dates: With VM version 3165, date values are held internally by the VM as the number of elapsed milliseconds since the "epoch" (January 1, 1970 00:00:00 UTC). There is no practical limit on the date range. This VM includes the Java 1.02 java.util.date class as well as the Java 1.1 java.util.calendar and related classes for date manipulation and storage. Two-digit shortcut handling: This VM handles the 2-digit year shortcut by applying an 80/20 sliding date window to place the 2-digit year in the expected century. This means 2-digit years are assumed to fall, from the current year, within the range of 20 years forward and 80 years backward. Example 1: if the year is 1998 and the date 1/6/17 is entered, it would be converted to a 4-digit year as 1/6/2017. Example 2: if the year is 1998 and the date 2/16/73 is entered, it would be converted to a 4-digit year as 2/3/1973. Issues addressed by 3165: This VM has resolved the 2/29/00 parser issue. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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
Midtown Madness 1.0 (English)
| - | ||
| None | ||
| None | ||
| None | ||
| 11 Aug 1999 | ||
|
How the product handles dates: None Two-digit shortcut handling: None What issues are there?: None Recommendations to meet compliance: None Common date usage errors: None Testing guidelines and recommendations: 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
Midtown Madness 1.0 (English Australian)
| - | ||
| None | ||
| None | ||
| None | ||
| 11 Aug 1999 | ||
|
How the product handles dates: None Two-digit shortcut handling: None What issues are there?: None Recommendations to meet compliance: None Common date usage errors: None Testing guidelines and recommendations: 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
Midtown Madness 1.0 (English British)
| - | ||
| None | ||
| None | ||
| None | ||
| 11 Aug 1999 | ||
|
How the product handles dates: None Two-digit shortcut handling: None What issues are there?: None Recommendations to meet compliance: None Common date usage errors: None Testing guidelines and recommendations: 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
Midtown Madness 1.0 (French)
| - | ||
| None | ||
| None | ||
| None | ||
| 11 Aug 1999 | ||
|
How the product handles dates: None Two-digit shortcut handling: None What issues are there?: None Recommendations to meet compliance: None Common date usage errors: None Testing guidelines and recommendations: 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
Midtown Madness 1.0 (German)
| - | ||
| None | ||
| None | ||
| None | ||
| 11 Aug 1999 | ||
|
How the product handles dates: None Two-digit shortcut handling: None What issues are there?: None Recommendations to meet compliance: None Common date usage errors: None Testing guidelines and recommendations: 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
Midtown Madness 1.0 (Japanese)
| - | ||
| None | ||
| None | ||
| None | ||
| 11 Aug 1999 | ||
|
How the product handles dates: None Two-digit shortcut handling: None What issues are there?: None Recommendations to meet compliance: None Common date usage errors: None Testing guidelines and recommendations: 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
Midtown Madness 1.0 (Spanish)
| - | ||
| None | ||
| None | ||
| None | ||
| 11 Aug 1999 | ||
|
How the product handles dates: None Two-digit shortcut handling: None What issues are there?: None Recommendations to meet compliance: None Common date usage errors: None Testing guidelines and recommendations: 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
MIFST 1.0 (English)
| 01 Jan 1900 - 28 Feb 2100 | ||
| None. | ||
| Windows NT 4.0 with Service Pack 3 or greater, Internet Information Server 3.0, SQL Server 6.5 with Service Pack 3 or greater, Internet Explorer 3.02 | ||
| System Clock. | ||
| 30 Oct 1998 | ||
|
Release Date: October 1997
How the product handles dates: In the OFX Gateway code, dates are stored in OLE Date format on the server and SQL dates in the database. No interfaces are provided which accept 2-digit dates.
In the web server code, two-digit date input is allowed via VBScript. In the case where the parameter is a DATE and a string is passed, Visual Basic converts the date string to the DATE variant type. Similarly, when text is imported as a parameter to calls (usually when the parameter is optional), VariantChangeType() (an OLE call) converts the string to a DATE. The web server code uses the following:
Two-digit shortcut handling: There is 2-digit shortcut handling only via the VBScript interface to the Data Services object on the web server.
Years specified as 00 through 29 are interpreted as 2000 through 2029. Years specified as 30 through 99 are interpreted as 1930 through 1999.
Testing guidelines and recommendations: When creating a Financial Institution Interface (FII) between the OFX Gateway and legacy systems, give special attention to the testing of any required date-conversion algorithms.
Furthermore, web authors creating sites that use the provided VBScript interface should remember that dates specified by two digits will be interpreted as falling within the range 1930-2029. Requiring customers to specify dates with 4-digit years would avoid this interpretive limitation. Note: In versions 1.0 and 1.01, leap years (including the year 2000) will be calculated correctly until the year 2100. The year 2100 is not a leap year, but will be recognized as one – as will all subsequent years divisible by 100. While this allows for the correct handling of the year 2000, it effectively limits the operational range of versions 1.0 and 1.01 to: Jan. 1, 1900 through Feb. 28, 2100 | ||
| 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
MIFST 1.01 (English)
| 01 Jan 1900 - 28 Feb 2100 | ||
| None. | ||
| Windows NT 4.0 with Service Pack 3 or greater, Internet Information Server 3.0, SQL Server 6.5 with Service Pack 3 or greater, Internet Explorer 3.02 | ||
| System Clock. | ||
| 30 Oct 1998 | ||
|
Release Date: October 1997How the product handles dates: In the OFX Gateway code, dates are stored in OLE Date format on the server and SQL dates in the database. No interfaces are provided which accept 2-digit dates. In the web server code, two-digit date input is allowed via VBScript. In the case where the parameter is a DATE and a string is passed, Visual Basic converts the date string to the DATE variant type. Similarly, when text is imported as a parameter to calls (usually when the parameter is optional), VariantChangeType() (an OLE call) converts the string to a DATE. The web server code uses the following:
Two-digit shortcut handling: There is 2-digit shortcut handling only via the VBScript interface to the Data Services object on the web server. Years specified as 00 through 29 are interpreted as 2000 through 2029. Years specified as 30 through 99 are interpreted as 1930 through 1999. Testing guidelines and recommendations: When creating a Financial Institution Interface (FII) between the OFX Gateway and legacy systems, give special attention to the testing of any required date-conversion algorithms. Furthermore, web authors creating sites that use the provided VBScript interface should remember that dates specified by two digits will be interpreted as falling within the range 1930-2029. Requiring customers to specify dates with 4-digit years would avoid this interpretive limitation. Note: In versions 1.0 and 1.01, leap years (including the year 2000) will be calculated correctly until the year 2100. The year 2100 is not a leap year, but will be recognized as one – as will all subsequent years divisible by 100. While this allows for the correct handling of the year 2000, it effectively limits the operational range of versions 1.0 and 1.01 to: Jan. 1, 1900 through Feb. 28, 2100 | ||
| 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.  | ||