01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Service Release 2 and Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98 or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Service Release 2 and Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Service Release 2 and Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Service Release 2 and Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98 or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Service Release 2 and Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Service Release 2 and Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
05 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How the product handles dates:
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Service Release 2 and Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Service Release 2 and Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Microsoft Thai Windows 95 or Thai Windows NT 4 (no specific SP is required) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How the product handles dates:
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 200 - 31 Dec 9999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Office 97 Service Release 2 and Microsoft Jet 3.5 Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.
Two-digit shortcut handling: Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way. 1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029 1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999 Common date usage errors:
To find more information on date related issues for this product:
Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office 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. |
01 Jan 100 - 31 Dec 9999 | |||||||||||||||||
none | |||||||||||||||||
Windows 95, or Windows NT 3.51 or greater; oleaut32.dll | |||||||||||||||||
System Clock | |||||||||||||||||
21 Jun 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. |
01 Jan 100 - 31 Dec 9999 | ||||||
None | ||||||
Windows 95, or Windows NT 3.51 or greater; oleaut32.dll | ||||||
System Clock | ||||||
21 Jun 1999 | ||||||
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications. The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls. The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx. The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing. The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates. Display and sorting are determined by the Regional Settings applet in the Control Panel. The Replication Manager and Transporter use Jet to store and manipulate data. It uses shared VBA components to perform calculations on Date/Time data. The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95. See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates. The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95. Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95. The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application. Two-digit shortcut handling: The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display. The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95. Common date usage errors: See the common pitfalls and testing methods used in Access 95. Testing guidelines and recommendations:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 100 - 31 Dec 9999 | ||||||
none | ||||||
Windows 95, or Windows NT 3.51 or greater; oleaut32.dll | ||||||
System Clock | ||||||
21 Jun 1999 | ||||||
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications. The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls. The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx. The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing. The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates. Display and sorting are determined by the Regional Settings applet in the Control Panel. The Replication Manager and Transporter use Jet to store and manipulate data. It uses shared VBA components to perform calculations on Date/Time data. The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95. See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates. The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95. Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95. The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application. Two-digit shortcut handling: The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display. The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95. Common date usage errors: See the common pitfalls and testing methods used in Access 95. Testing guidelines and recommendations:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 100 - 31 Dec 9999 | ||||||
none | ||||||
Windows 95, or Windows NT 3.51 or greater; oleaut32.dll | ||||||
System Clock | ||||||
21 Jun 1999 | ||||||
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications. The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls. The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx. The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing. The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates. Display and sorting are determined by the Regional Settings applet in the Control Panel. The Replication Manager and Transporter use Jet to store and manipulate data. It uses shared VBA components to perform calculations on Date/Time data. The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95. See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates. The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95. Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95. The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application. Two-digit shortcut handling: The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display. The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95. Common date usage errors: See the common pitfalls and testing methods used in Access 95. Testing guidelines and recommendations:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 100 - 31 Dec 9999 | ||||||
none | ||||||
Windows 95, or Windows NT 3.51 or greater; oleaut32.dll | ||||||
System Clock | ||||||
21 Jun 1999 | ||||||
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications. The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls. The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx. The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing. The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates. Display and sorting are determined by the Regional Settings applet in the Control Panel. The Replication Manager and Transporter use Jet to store and manipulate data. It uses shared VBA components to perform calculations on Date/Time data. The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95. See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates. The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95. Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95. The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application. Two-digit shortcut handling: The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display. The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95. Common date usage errors: See the common pitfalls and testing methods used in Access 95. Testing guidelines and recommendations:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 100 - 31 Dec 9999 | ||||||
none | ||||||
Windows 95, or Windows NT 3.51 or greater; oleaut32.dll | ||||||
System Clock | ||||||
21 Jun 1999 | ||||||
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications. The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls. The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx. The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing. The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates. Display and sorting are determined by the Regional Settings applet in the Control Panel. The Replication Manager and Transporter use Jet to store and manipulate data. It uses shared VBA components to perform calculations on Date/Time data. The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95. See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates. The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95. Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95. The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application. Two-digit shortcut handling: The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display. The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95. Common date usage errors: See the common pitfalls and testing methods used in Access 95. Testing guidelines and recommendations:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 100 - 31 Dec 9999 | ||||||
none | ||||||
Windows 95, or Windows NT 3.51 or greater; oleaut32.dll | ||||||
System Clock | ||||||
21 Jun 1999 | ||||||
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications. The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls. The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx. The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing. The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates. Display and sorting are determined by the Regional Settings applet in the Control Panel. The Replication Manager and Transporter use Jet to store and manipulate data. It uses shared VBA components to perform calculations on Date/Time data. The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95. See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates. The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95. Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95. The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application. Two-digit shortcut handling: The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display. The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95. Common date usage errors: See the common pitfalls and testing methods used in Access 95. Testing guidelines and recommendations:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 100 - 31 Dec 9999 | |||||||||||||||||
none | |||||||||||||||||
Windows 95, or Windows NT 3.51 or greater; oleaut32.dll | |||||||||||||||||
System Clock | |||||||||||||||||
21 Jun 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. |
01 Jan 100 - 31 Dec 9999 | ||||||
none | ||||||
Windows 95, or Windows NT 3.51 or greater; oleaut32.dll | ||||||
System Clock | ||||||
21 Jun 1999 | ||||||
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications. The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls. The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx. The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing. The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates. Display and sorting are determined by the Regional Settings applet in the Control Panel. The Replication Manager and Transporter use Jet to store and manipulate data. It uses shared VBA components to perform calculations on Date/Time data. The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95. See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates. The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95. Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95. The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application. Two-digit shortcut handling: The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display. The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95. Common date usage errors: See the common pitfalls and testing methods used in Access 95. Testing guidelines and recommendations:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
01 Jan 1998 - 31 Dec 2007 | ||
NONE | ||
Windows 95, Windows NT 4.0, all Oem Service Releases, all Service Packs, and greater | ||
Clock internal to the doll | ||
07 Jul 1999 | ||
The ActiMates dolls contain an internal clock. This clock references an internal hard-coded look-up table of major holidays with varied calendar days (i.e. Easter, Thanksgiving) through 12/31/2007. What are the issues?: After 12/31/2007, lose some minor functionality. First, only fixed holidays (i.e. Independence Day) will be recognized and announced by the character after this date. In addition, the character will not recite the year when announcing the date and time. No immediate action is required to have the doll maintain functionality through the change in the millennium. |
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. |
- | ||
07 Jul 1999 | ||
Description of how the product handles dates: ActiMates Barney does not maintain an internal clock. There are no date issues with this product. |
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. |
01 Jan 1998 - 31 Dec 2007 | ||
NONE | ||
Windows 95, Windows NT 4.0, all Oem Service Releases, all Service Packs, and greater | ||
Clock internal to the doll | ||
07 Jul 1999 | ||
The ActiMates dolls contain an internal clock. This clock references an internal hard-coded look-up table of major holidays with varied calendar days (i.e. Easter, Thanksgiving) through 12/31/2007. What are the issues?: After 12/31/2007, lose some minor functionality. First, only fixed holidays (i.e. Independence Day) will be recognized and announced by the character after this date. In addition, the character will not recite the year when announcing the date and time. No immediate action is required to have the doll maintain functionality through the change in the millennium. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
01 Jan 1900 - 31 Dec 2099 | ||
None | ||
Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX. | ||
System Clock, DCOM, COMCTL, OLEAUT32 | ||
14 Jul 1999 | ||
Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance. See DirectX Media for information about newer versions of this product.How the product handles dates: ActiveMovie internals do not manipulate dates. A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie. Two-digit shortcut handling: Not applicable. Testing guidelines and recommendations: Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems. |
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. |
- | ||
None | ||
Windows NT 4.0 Service Pack 3 or higher, Internet Explorer 4.X or higher, SQL Server 6.5 Service Pack 3 or higher, ADO 2.1, MSMQ 1.0 or higher. | ||
None | ||
22 Jun 1999 | ||
How the product handles dates: This product does not perform date calculations. There are no interfaces (user interface or programmatic) to provide dates to System Framework Services. This product does not deal with dates directly. There is no ActiveStore System Framework Services source code that uses dates, but it uses SQL Server, ADO, Visual C 6.0, and Visual Basic 6.0 that might use dates. Two-digit shortcut handling: Not Applicable.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
None | ||
Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC | ||
Windows CE OEM, Windows CE Operating System | ||
21 Sep 1999 | ||
Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.How the product handles dates: ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates. ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software. On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date). OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069. For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.
Two-digit shortcut handling: Not Applicable.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back. |
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. |
- | ||
None | ||
Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC | ||
Windows CE OEM, Windows CE Operating System | ||
21 Sep 1999 | ||
Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.How the product handles dates: ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates. ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software. On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date). OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069. For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.
Two-digit shortcut handling: Not Applicable.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back. |
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. |
- | ||
None | ||
Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC | ||
Windows CE OEM, Windows CE Operating System | ||
21 Sep 1999 | ||
Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.How the product handles dates: ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates. ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software. On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date). OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069. For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.
Two-digit shortcut handling: Not Applicable.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back. |
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. |
- | ||
None | ||
Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC | ||
Windows CE OEM, Windows CE Operating System | ||
21 Sep 1999 | ||
Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.How the product handles dates: ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates. ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software. On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date). OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069. For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.
Two-digit shortcut handling: Not Applicable.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back. |
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. |
- | ||
None | ||
Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC | ||
Windows CE OEM, Windows CE Operating System | ||
09 Nov 1999 | ||
Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.How the product handles dates: ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates. ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software. On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date). OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069. For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.
Two-digit shortcut handling: Not Applicable.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back. |
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. |
- | ||
None | ||
Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC | ||
Windows CE OEM, Windows CE Operating System | ||
21 Sep 1999 | ||
Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.How the product handles dates: ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates. ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software. On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date). OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069. For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.
Two-digit shortcut handling: Not Applicable.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back. |
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. |
- | ||
None | ||
Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC | ||
Windows CE OEM, Windows CE Operating System | ||
21 Sep 1999 | ||
Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.How the product handles dates: ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates. ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software. On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date). OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069. For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.
Two-digit shortcut handling: Not Applicable.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1996 How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1997 Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1998 Version 2.0 shipped in Visual Studio. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1998 Version 2.0 shipped in Visual Studio. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1998 Version 2.0 shipped in Visual Studio. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1998 Version 2.0 shipped in Visual Studio. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1998 Version 2.0 shipped in Visual Studio. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1998 Version 2.0 shipped in Visual Studio. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1998 Version 2.0 shipped in Visual Studio. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1998 Version 2.0 shipped in Visual Studio. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems | ||
OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll | ||
NONE | ||
11 Nov 1998 | ||
Operational Range for Data: Data Source DependentRelease Date: 1998 Version 2.0 shipped in Visual Studio. How the product handles dates: ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service. Two-digit shortcut handling: OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion. Common date usage errors: Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. 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 OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store. |
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. |
- | ||
None | ||
DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT | ||
System clock | ||
14 Oct 1999 | ||
This document applies to: Age of Empires v.1 (released September 14, 1997) Age of Empires: Rise of Rome v.1 (released September 17, 1998) Age of Empires Gold Edition v.1 (released January 10, 1999) How the product handles dates: Age of Empires does not accept user entered dates. Two-digit shortcut handling: Not Applicable. Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included. Age of Empires v.1 MSInfo versions 2.51.0.0808 Internet Explorer version 3.02 Age of Empires: Rise of Rome v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 MS Sampler version 1.00.0005, which is a shell that launches the following applications: Urban Assault Close Combat 2 Gaming Zone A501 Age of Empires Gold Edition v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 DirectPlay 6.0a MS Sampler version 1.00.0005, which is a shell that launches the following applications: Gaming Zone A501
|
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. |
- | ||
None | ||
DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT | ||
System clock | ||
14 Oct 1999 | ||
This document applies to: Age of Empires v.1 (released September 14, 1997) Age of Empires: Rise of Rome v.1 (released September 17, 1998) Age of Empires Gold Edition v.1 (released January 10, 1999) How the product handles dates: Age of Empires does not accept user entered dates. Two-digit shortcut handling: Not Applicable. Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included. Age of Empires v.1 MSInfo versions 2.51.0.0808 Internet Explorer version 3.02 Age of Empires: Rise of Rome v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 MS Sampler version 1.00.0005, which is a shell that launches the following applications: Urban Assault Close Combat 2 Gaming Zone A501 Age of Empires Gold Edition v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 DirectPlay 6.0a MS Sampler version 1.00.0005, which is a shell that launches the following applications: Gaming Zone A501
|
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. |
- | ||
None | ||
DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT | ||
System clock | ||
14 Oct 1999 | ||
This document applies to: Age of Empires v.1 (released September 14, 1997) Age of Empires: Rise of Rome v.1 (released September 17, 1998) Age of Empires Gold Edition v.1 (released January 10, 1999) How the product handles dates: Age of Empires does not accept user entered dates. Two-digit shortcut handling: Not Applicable. Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included. Age of Empires v.1 MSInfo versions 2.51.0.0808 Internet Explorer version 3.02 Age of Empires: Rise of Rome v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 MS Sampler version 1.00.0005, which is a shell that launches the following applications: Urban Assault Close Combat 2 Gaming Zone A501 Age of Empires Gold Edition v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 DirectPlay 6.0a MS Sampler version 1.00.0005, which is a shell that launches the following applications: Gaming Zone A501
|
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. |
- | ||
None | ||
DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT | ||
System clock | ||
14 Oct 1999 | ||
This document applies to: Age of Empires v.1 (released September 14, 1997) Age of Empires: Rise of Rome v.1 (released September 17, 1998) Age of Empires Gold Edition v.1 (released January 10, 1999) How the product handles dates: Age of Empires does not accept user entered dates. Two-digit shortcut handling: Not Applicable. Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included. Age of Empires v.1 MSInfo versions 2.51.0.0808 Internet Explorer version 3.02 Age of Empires: Rise of Rome v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 MS Sampler version 1.00.0005, which is a shell that launches the following applications: Urban Assault Close Combat 2 Gaming Zone A501 Age of Empires Gold Edition v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 DirectPlay 6.0a MS Sampler version 1.00.0005, which is a shell that launches the following applications: Gaming Zone A501
|
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. |
- | ||
None | ||
DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT | ||
System clock | ||
14 Oct 1999 | ||
This document applies to: Age of Empires v.1 (released September 14, 1997) Age of Empires: Rise of Rome v.1 (released September 17, 1998) Age of Empires Gold Edition v.1 (released January 10, 1999) How the product handles dates: Age of Empires does not accept user entered dates. Two-digit shortcut handling: Not Applicable. Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included. Age of Empires v.1 MSInfo versions 2.51.0.0808 Internet Explorer version 3.02 Age of Empires: Rise of Rome v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 MS Sampler version 1.00.0005, which is a shell that launches the following applications: Urban Assault Close Combat 2 Gaming Zone A501 Age of Empires Gold Edition v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 DirectPlay 6.0a MS Sampler version 1.00.0005, which is a shell that launches the following applications: Gaming Zone A501
|
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. |
- | ||
None | ||
DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT | ||
System clock | ||
14 Oct 1999 | ||
This document applies to: Age of Empires v.1 (released September 14, 1997) Age of Empires: Rise of Rome v.1 (released September 17, 1998) Age of Empires Gold Edition v.1 (released January 10, 1999) How the product handles dates: Age of Empires does not accept user entered dates. Two-digit shortcut handling: Not Applicable. Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included. Age of Empires v.1 MSInfo versions 2.51.0.0808 Internet Explorer version 3.02 Age of Empires: Rise of Rome v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 MS Sampler version 1.00.0005, which is a shell that launches the following applications: Urban Assault Close Combat 2 Gaming Zone A501 Age of Empires Gold Edition v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 DirectPlay 6.0a MS Sampler version 1.00.0005, which is a shell that launches the following applications: Gaming Zone A501
|
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. |
- | ||
None | ||
DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT | ||
System clock | ||
14 Oct 1999 | ||
This document applies to: Age of Empires v.1 (released September 14, 1997) Age of Empires: Rise of Rome v.1 (released September 17, 1998) Age of Empires Gold Edition v.1 (released January 10, 1999) How the product handles dates: Age of Empires does not accept user entered dates. Two-digit shortcut handling: Not Applicable. Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included. Age of Empires v.1 MSInfo versions 2.51.0.0808 Internet Explorer version 3.02 Age of Empires: Rise of Rome v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 MS Sampler version 1.00.0005, which is a shell that launches the following applications: Urban Assault Close Combat 2 Gaming Zone A501 Age of Empires Gold Edition v.1 MSInfo versions 2.51.0.0808 Adobe Acrobat Reader version 3.01 DX5Test version 1.0 DX Diag version 4.06.00.0318 DX Info version 4.05.00.0155 DX Tool version 4.05.00.0155 DirectPlay 6.0a MS Sampler version 1.00.0005, which is a shell that launches the following applications: Gaming Zone A501
|
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. |
15 Sep 1999 - 31 Dec 2035 | ||
None | ||
DirectX 6.1, DirectPlay 6.1a | ||
System clock | ||
14 Oct 1999 | ||
How the product handles dates: Microsoft Age of Empires II: The Age of Kings stores dates for recorded games in the following format: recorded game – DD-month-YYYY time(hh`mm`ss) Example: recorded game – 31-Dec-2000 00`36`32 Two-digit shortcut handling: The product does not use 2-digit-year shortcuts. |
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. |
15 Sep 1999 - 31 Dec 2035 | ||
None | ||
DirectX 6.1, DirectPlay 6.1a | ||
System clock | ||
14 Oct 1999 | ||
How the product handles dates: Microsoft Age of Empires II: The Age of Kings stores dates for recorded games in the following format: recorded game – DD-month-YYYY time(hh`mm`ss) Example: recorded game – 31-Dec-2000 00`36`32 Two-digit shortcut handling: The product does not use 2-digit-year shortcuts. |
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. |
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. |