- | ||
Latest version of MDAC | ||
Windows NT Server 4.0 with Service Pack 3 | ||
Uses the operating system date/time routines | ||
28 Oct 1999 | ||
Operational Range for Data: VARIANT DATE range Jan 1, 1753 – Dec 31, 2078 inclusiveRelease Date: 2Q/1998 There could be some Y2K issues with the version of MDAC components installed by NetShow. Although, no Y2K issues concerning Netshow have been found, please refer to the MDAC Y2K compliance document for further information. The latest MDAC version can be download from HTTP://www.microsoft.com/data.How the product handles dates:
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | |||||||||||
Latest version of MDAC | |||||||||||
Windows NT Server 4.0 with Service Pack 3 | |||||||||||
Uses the operating system date/time routines | |||||||||||
30 Jul 1999 | |||||||||||
How the product handles dates:
Events from the server are sent in SystemTime format and then converted to VariantTime before being output via automation. These are all based on GMT, which then allows the client to convert to the local time zone. The resulting data is then used in two places. The first is stored in Access date format to a database, and the other is displayed to a running monitor window via a call to GetTimeFormat and GetDateFormat using user default and DATE_SHORTDATE, TIME_FORCE24HOURFORMAT. Title attributes such as creation time are stored as FileTime format.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | |||||||||||||
Latest version of MDAC | |||||||||||||
Windows NT Server 4.0 with Service Pack 3 | |||||||||||||
Uses the operating system date/time routines | |||||||||||||
30 Jul 1999 | |||||||||||||
There could be some Y2K issues with the version of MDAC components installed by NetShow. Although, no Y2K issues concerning Netshow have been found, please refer to the MDAC Y2K compliance document for further information. The latest MDAC version can be download from HTTP://www.microsoft.com/data.How the product handles dates:
Events from the server are sent in SystemTime format and then converted to VariantTime before being output via automation. These are all based on GMT, which then allows the client to convert to the local time zone. The resulting data is then used in two places. The first is stored in Access date format to a database. This is accomplished by data access object components which programmatically create an Access database. The other is displayed to a running monitor window via a call to GetTimeFormat and GetDateFormat using user default and DATE_SHORTDATE, TIME_FORCE24HOURFORMAT. Title attributes such as creation time are stored as FileTime format.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 1980 - 31 Dec 2099 | ||
None | ||
None | ||
None | ||
30 Aug 1999 | ||
How the product handles dates: This product does not handle dates or perform 2-digit shortcut interpretations. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Compliant versions of Windows NT 3.51 or Windows 95, msvcrt.dll, mfc40.dll | ||
None | ||
datetime data will correspond to the data source. ODBC drivers use the system clock to supply the date when converting from time (no date specified) to date-time. | ||
03 Apr 1999 | ||
Operational Range for Data: Dependent on Data SourceRelease Date: 1995 Product: Microsoft ODBC core components (Driver manager, Cursor library, ODBC Administrator) ODBC is a Data Access application programming interface (API) that exposes data from a variety of Data Sources. How the product handles dates: ODBC standard date syntax and escape formats disallow the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, Microsoft recommends using 4-digit year formats in dates, particularly when placing data into a store and querying that store. Platforms applicable: x86 and Alpha machines. Power PC and MIPS were not tested, as support for these platforms has been discontinued. Known Issues: In ODBC 2.x , there are two installer APIs with year 2000 issues. The APIs in question are: SQLInstallDriver and SQLInstallODBC. These APIs were used to write custom setups for ODBC drivers. SQLInstallODBC was discontinued after ODBC 2.5. SQLInstallDriver still exists in later versions of ODBC, but the option to use an INF (the source of the problem), was removed in ODBC 3.0. In addition, ODBC 3.0 added a new preferred API, SQLInstallDriverEx. Under what circumstances would the problem occur? If someone wrote a setup using SQLInstallDriver or SQLInstallODBC from ODBC 2.5, AND they used an INF, THEN during install, the date evaluation may not be done properly, resulting in wrong files version being installed, or files being installed with incorrect filedates. The installer APIs are in odbccp32.dll for 32bit apps, and in odbcinst.dll for 16bit apps. Remediation: The remediation is to use ODBC 3.0 or higher. ODBC 3.x does not support SQLInstallODBC, and does not support SQLInstallDriver with INFs, so the application would get a warning during setup, instead of possibly installing wrong bits. To determine which version of ODBC is installed, look at the fileversion of odbc32.dll (right click/properties). If it is 2.50.xxxx, it is ODBC 2.5. If it is 3.00.0000 or higher, it is ODBC 3.0 or greater.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
- | ||
Compliant versions of Windows NT 3.51, msvcrt.dll, mfc40.dll | ||
None | ||
datetime data will correspond to the data source.ODBC drivers use the system clock to supply the date when converting from time (no date specified) to date-time. | ||
11 Aug 1999 | ||
Operational Range for Data: Dependent on Data SourceRelease Date: 1995 Product: Microsoft ODBC core components (Driver manager, Cursor library, ODBC Administrator) ODBC is a Data Access application programming interface (API) that exposes data from a variety of Data Sources. How the product handles dates: ODBC standard date syntax and escape formats disallow the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, Microsoft recommends using 4-digit year formats in dates, particularly when placing data into a store and querying that store. Platforms applicable: x86 machines. Power PC and MIPS were not tested, as support for these platforms has been discontinued. In addition, Alpha machines were not tested. Known Issues: In ODBC 2.x, there are two installer APIs with year 2000 issues. The APIs in question are: SQLInstallDriver and SQLInstallODBC. These APIs were used to write custom setups for ODBC drivers. SQLInstallODBC was discontinued after ODBC 2.5. SQLInstallDriver still exists in later versions of ODBC, but the option to use an INF (the source of the problem), was removed in ODBC 3.0. In addition, ODBC 3.0 added a new preferred API, SQLInstallDriverEx. Under what circumstances would the problem occur? If someone wrote a setup using SQLInstallDriver or SQLInstallODBC from ODBC 2.5, AND they used an INF, THEN during install, the date evaluation may not be done properly, resulting in wrong files version being installed, or files being installed with incorrect filedates. The installer APIs are in odbccp32.dll for 32bit apps, and in odbcinst.dll for 16bit apps. Remediation: The remediation is to use ODBC 3.0 or higher. ODBC 3.x does not support SQLInstallODBC, and does not support SQLInstallDriver with INFs, so the application would get a warning during setup, instead of possibly installing wrong bits. To determine which version of ODBC is installed, look at the fileversion of odbc32.dll (right click/properties). If it is 2.50.xxxx, it is ODBC 2.5. If it is 3.00.xxxx or higher, it is ODBC 3.0 or greater.
|
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
10 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.0 - shipped with MS Office ’97 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
10 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source. | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information ServerODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.51 - shipped with MDAC 2.0 and MS Visual Studio ‘98 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.51 - shipped with MDAC 2.0 and MS Visual Studio ‘98 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.51 - shipped with MDAC 2.0 and MS Visual Studio ‘98 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.51 - shipped with MDAC 2.0 and MS Visual Studio ‘98 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.51 - shipped with MDAC 2.0 and MS Visual Studio ‘98 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.51 - shipped with MDAC 2.0 and MS Visual Studio ‘98 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source | ||
22 Feb 1999 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.51 - shipped with MDAC 2.0 and MS Visual Studio 6.0. ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.51 - shipped with MDAC 2.0 and MS Visual Studio ‘98 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 NT4 sp3 or higher, or Windows 9x operating systems. | ||
OLEAUT, msvcrt.dll, mtxdm.dll | ||
None- except that datetime data will always correspond to the data source | ||
11 Nov 1998 | ||
Operational Range for Data: Dependent on Data SourceODBC 3.51 - shipped with MDAC 2.0 and MS Visual Studio ‘98 ODBC is a Data Access API that exposes data from a variety of Data Sources How the product handles dates: ODBC date syntax and escape formats prevent the use of anything but 'YYYY' for the year portion of a date or a TIMESTAMP/DATE structure. Two-digit shortcut handling: The product does not handle dates in 2-digit formats. Please note that although not recommended, application developers may pass a 2-digit date as a literal to the server, in which case the interpretation is left up to the server. Common date usage errors: ODBC is neutral in this regard. Date usage errors are data source dependent, not ODBC dependent. Testing guidelines and recommendations: Since there is some "windowing" inherent in the date interpretation features of most backend data stores, users should always 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
02 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
17 Jul 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value?s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program?s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||||||||||
02 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||
16 Jun 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 2000 Premium version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Premium, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as 4 digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in 4 digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed, for example, to between 1950-2049. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider all instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: any number before a certain point is assumed to be in the 1900s, and any number after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99 they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0, which can be used to create compliant solutions based on Office programs, these same rules apply whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide.For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last 2 digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915, is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such a misinterpretation can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is always some potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
04 Aug 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
04 Aug 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
04 Aug 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value?s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program?s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||
25 Oct 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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 | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
Product specific; see the links to product guides in the table below | ||||||||||||||||||||||||||||||||||
18 Jul 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 Professional 2000 version 9.0 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office 2000 Professional, summarizes how they handle dates, and lists their operational ranges. For more information, see links to specific product guides.
There are some simple steps users can take to avoid having confusing date formats in their Office programs, such as using 4-digit years and changing the date settings in their operating system. Even in those Office programs that are not necessarily used for performing calculations, such as Word and PowerPoint, it is a good idea for users to use 4-digit years so that they and others who work in their documents can differentiate between dates. It is easy to change how the date is read and displayed so that years are presented as four digits. That is, the operating system date settings can be changed so that when 2/23/01 is entered, the program automatically displays the year in four digits as 2/23/2001. Planning for 4-digit-year display is important in programs such as Excel, where column widths may be fixed by the worksheet author with widths that are too narrow for 4-digit years. To change the system date format to display 4-digit years:
In Microsoft Windows 98, users can change the way 2-digit years are interpreted. Instead of having the program interpret 2-digit years between 1930-2029 (the default time period), the period can be changed--to between 1950-2049, for example. Changing the operating system may help avoid date mistakes in the Office software. Because this change has broad impact on 2-digit date handling, including that in Microsoft Visual Basic (VB) and Microsoft Visual Basic for Applications (VBA), before making the change, users should consider the instances of where 2-digit years may be handled in Office or in their operating system. To change the way 2-digit years are interpreted:
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The code uses a 100-year date window: anything before a certain point is assumed to be in the 1900s, and anything after that point is in the 2000s. Unless the user specifies otherwise, the code assumes that when a user enters a 2-digit year with a value from 00 to 29, they mean the years 2000-2029, and if they enter 30 to 99, they mean the years 1930-1999. The user can change the date window in Windows 98 by following the procedure above to change the way 2-digit years are interpreted. Or they can change the date in the registry by creating or navigating to the registry key HKEY_CURRENT_USER\Control Panel\International\Calendars\TwoDigitYearMax, adding or finding the string value "1," and then changing that value’s data to reflect the end year wanted. If the user changes the end year on the Date tab in Regional Settings to "2050," any 2-digit values from 00 to 49 are interpreted as the years 2000-2049, and those values from 50 to 99 are interpreted as the years 1950-1999. For the shared technology Visual Basic for Applications version 6.0--which can be used to create compliant solutions based on Office programs--these same rules apply to all dates whether the date is used by an intrinsic function, it is directly entered into an Office program, or its information is assigned to a file attribute using VBA. For more information, see the Visual Basic for Applications 6.0 product guide, which will be available in April. For Office setup functionality, because the Microsoft Windows installer uses dates to compare information already stored on a system, the installer relies on system date operations to ensure Year 2000 and backward compatibility. The Office Find Fast utility uses dates to determine how often to update information and as search criteria for users in a program’s Open dialog box (File menu). Find Fast reads in dates from either system date calls or Office documents and then stores the dates in full 4-digit-year format. Two-digit shortcut handling: Some programs support 2-digit shortcuts. For information about how a specific program converts 2-digit years to 4-digit formats, search for the product in the Products list in the Year 2000 Product Guide.Common date usage errors: If a date is pasted from one program into another using only the last two digits of the year, the date might be interpreted differently than the originating program interpreted it. Example: The date January 1, 1915 is in a non-Excel program. The date is copied, but because the system settings are "M/d/yy," all that is copied is the text "1/1/15." When "1/1/15" is pasted into Excel, Excel interprets the date as January 1, 2015. Such an issue can also occur when one program is using an "M/d/yy" format while another is using a "d/M/yy" format. Due to the ambiguous nature of text dates, there is potential for error. Serial dates should be used whenever possible and great care taken when transferring text dates. For more information about common date usage issues in a specific program, search for the product in the Products list in the Year 2000 Product Guide.Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. For product-specific testing guidelines and recommendations, search for the product in the Products list in the Year 2000 Product Guide. |
The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
The product is compliant . Software updates 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. |