Microsoft TechNet ITHome - Microsoft Year 2000 Product Guide
Microsoft Products
Product Entry Guide Detail


The Microsoft Year 2000 Resource Center Product Guide details specific Year 2000 information concerning Microsoft products. The information in the product guide is presented to assist IT professionals in planning their transition to the Year 2000. If you cannot find a specific product and it is not on the "Microsoft Products: Testing Yet to be Completed" list, you can assume it will NOT be tested for compliancy.
Microsoft will continually update the Year 2000 Product Guide with the most current Year 2000 test information. Visit the Year 2000 Product Guide for more details regarding the Microsoft Compliance Categories.

------------------------
Microsoft Year 2000 Resource Center
NetShow  3.0   (English)

Product Summary
Product: NetShow Version: 3.0 Category:Compliant*
Language: English OS: Win NT Release Date: N/A
Operational Range: -
Prerequisites: Latest version of MDAC
Product Dependencies: Windows NT Server 4.0 with Service Pack 3
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 28 Oct 1999
Product Details

Operational Range for Data: VARIANT DATE range Jan 1, 1753 – Dec 31, 2078 inclusive

Release 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:

  • 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.

 

 

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
NetShow Theater Svr  3.0   (English)

Product Summary
Product: NetShow Theater Svr Version: 3.0 Category:Compliant*
Language: English OS: Win NT Release Date: 01 Jun 1998
Operational Range: -
Prerequisites: Latest version of MDAC
Product Dependencies: Windows NT Server 4.0 with Service Pack 3
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 30 Jul 1999
Product Details

Release 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:

      

 

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.

      

 NetShow Theater Server 3.0 contains the following Data Access Object (DAO) components to programmatically create a Access database:

----- W32i DLL ENU      3.51.623.4 shp  1,045,776 04-13-98 msjet35.dll
----- W32i DLL ENU      3.51.623.0 shp    123,664 04-13-98 msjint35.dll
----- W32i DLL ENU      3.51.623.0 shp     24,848 04-13-98 msjter35.dll
----- W32i DLL ENU      3.0.0.6908 shp     18,192 04-13-98 vbajet32.dll
----- W32i DLL ENU      3.0.0.6908 shp    368,912 04-13-98 vbar332.dll


Two-digit shortcut handling:

NetShow Theater Server: .

      


NetShow Theater server stores the title creation times in FileTime format.  NetShow Theater server also writes a client logging text file that contains the date in the format YYYY-MM-DD.  No other dates are exposed from the NetShow Theater server.



Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
NetShow Theater Svr  3.0   (Japanese)

Product Summary
Product: NetShow Theater Svr Version: 3.0 Category:Compliant*
Language: Japanese OS: Win NT Release Date: 21 Aug 1998
Operational Range: -
Prerequisites: Latest version of MDAC
Product Dependencies: Windows NT Server 4.0 with Service Pack 3
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 30 Jul 1999
Product Details

 Release 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:

      

 

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.

      

 


Two-digit shortcut handling:
Japanese NetShow Theater Server: N/A. Japanese NetShow Theater server stores the title creation times in FileTime format.  Japanese NetShow Theater server also writes a client logging text file that contains the date in the format YYYY-MM-DD.  No other dates are exposed from the Japanese NetShow Theater server.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
NFL Fever 2000  1.0   (English)

Product Summary
Product: NFL Fever 2000 Version: 1.0 Category:Compliant
Language: English OS: 32-Bit Win Release Date: 14 Jul 1999
Operational Range: 01 Jan 1980 - 31 Dec 2099
Prerequisites: None
Product Dependencies: None
Clock Dependencies: None
Last Updated: 30 Aug 1999
Product Details

How the product handles dates:

This product does not handle dates or perform 2-digit shortcut interpretations.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  2.5   (English)

Product Summary
Product: ODBC Core Components Version: 2.5 Category:Compliant*#
Language: English OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Compliant versions of Windows NT 3.51 or Windows 95, msvcrt.dll, mfc40.dll
Product Dependencies: None
Clock Dependencies: 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.
Last Updated: 03 Apr 1999
Product Details

Operational Range for Data: Dependent on Data Source

Release 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.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  2.5   (Japanese)

Product Summary
Product: ODBC Core Components Version: 2.5 Category:Compliant*#
Language: Japanese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Compliant versions of Windows NT 3.51, msvcrt.dll, mfc40.dll
Product Dependencies: None
Clock Dependencies: 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.
Last Updated: 11 Aug 1999
Product Details

Operational Range for Data: Dependent on Data Source

Release 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (Danish)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: Danish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 10 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (Dutch)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: Dutch OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (English)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: English OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (Finnish)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: Finnish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (French)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: French OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (German)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: German OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (Italian)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: Italian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (Japanese)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: Japanese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (Norwegian)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: Norwegian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (Russian)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: Russian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (Spanish)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: Spanish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.0   (Swedish)

Product Summary
Product: ODBC Core Components Version: 3.0 Category:Compliant*
Language: Swedish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Chinese - Simplified)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Chinese - Simplified OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Chinese - Traditional)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Chinese - Traditional OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Czech)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Czech OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Danish)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Danish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Dutch)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Dutch OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (English)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: English OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Finnish)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Finnish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (French)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: French OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (German)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: German OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Greek)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Greek OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Hungarian)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Hungarian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Italian)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Italian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Japanese)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Japanese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Korean)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Korean OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Norwegian)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Norwegian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Polish)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Polish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Portuguese (Brazil))

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 10 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Portuguese)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Portuguese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Russian)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Russian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Slovak)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Slovak OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Slovenian)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Slovenian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Spanish)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Spanish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Swedish)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Swedish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.5   (Turkish)

Product Summary
Product: ODBC Core Components Version: 3.5 Category:Compliant*
Language: Turkish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source.
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 3.5 - shipped with MDAC 1.5 and Windows NT Option Pack: Internet Information Server

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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.51   (Chinese - Simplified)

Product Summary
Product: ODBC Core Components Version: 3.51 Category:Compliant*
Language: Chinese - Simplified OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.51   (Chinese - Traditional)

Product Summary
Product: ODBC Core Components Version: 3.51 Category:Compliant*
Language: Chinese - Traditional OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.51   (English)

Product Summary
Product: ODBC Core Components Version: 3.51 Category:Compliant*
Language: English OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.51   (French)

Product Summary
Product: ODBC Core Components Version: 3.51 Category:Compliant*
Language: French OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.51   (German)

Product Summary
Product: ODBC Core Components Version: 3.51 Category:Compliant*
Language: German OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.51   (Italian)

Product Summary
Product: ODBC Core Components Version: 3.51 Category:Compliant*
Language: Italian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.51   (Japanese)

Product Summary
Product: ODBC Core Components Version: 3.51 Category:Compliant*
Language: Japanese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source
Last Updated: 22 Feb 1999
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.51   (Korean)

Product Summary
Product: ODBC Core Components Version: 3.51 Category:Compliant*
Language: Korean OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
ODBC Core Components  3.51   (Spanish)

Product Summary
Product: ODBC Core Components Version: 3.51 Category:Compliant*
Language: Spanish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT4 sp3 or higher, or Windows 9x operating systems.
Product Dependencies: OLEAUT, msvcrt.dll, mtxdm.dll
Clock Dependencies: None- except that datetime data will always correspond to the data source
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Dependent on Data Source

ODBC 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.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Chinese - Simplified)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Chinese - Simplified OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Chinese - Traditional)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Chinese - Traditional OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Czech)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Czech OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Danish)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Danish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Dutch)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Dutch OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (English)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: English OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 02 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Finnish)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Finnish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (French)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: French OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (German)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: German OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Italian)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Italian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Japanese)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Japanese OS: 32-Bit Win Release Date: 09 Jul 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 17 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Korean)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Korean OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Norwegian)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Norwegian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 02 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Pan-Chinese)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Pan-Chinese OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Polish)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Polish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Portuguese (Brazil))

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Portuguese)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Portuguese OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Russian)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Russian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Spanish)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Spanish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Premium  9.0   (Swedish)

Product Summary
Product: Office 2000 Premium Version: 9.0 Category:Compliant
Language: Swedish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 16 Jun 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

 

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as 2 digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

FrontPage 2000

Dates are stored, calculated, compared, and sequenced in a 4-digit format.

01/01/1970 through 12/31/2036

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PhotoDraw 2000

Only dates that are provided by the operating system, such as the Created, Modified, and Accessed dates, are handled by this imaging program. These dates are in 4-digit-year formats.

System dependent

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a two-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Arabic)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Arabic OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 04 Aug 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Chinese - Simplified)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Chinese - Simplified OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Chinese - Traditional)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Chinese - Traditional OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Croatian)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Croatian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Czech)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Czech OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Danish)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Danish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Dutch)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Dutch OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (English)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: English OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (English Australian)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: English Australian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (English British)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: English British OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Estonian)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Estonian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Finnish)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Finnish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (French)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: French OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (German)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: German OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Greek)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Greek OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Hebrew)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Hebrew OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 04 Aug 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Hindu)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Hindu OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 04 Aug 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Hungarian)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Hungarian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Italian)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Italian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Japanese)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Japanese OS: 32-Bit Win Release Date: 09 Jul 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Korean)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Korean OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Latvian)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Latvian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Lithuanian)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Lithuanian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Norwegian)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Norwegian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Pan-Chinese)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Pan-Chinese OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Polish)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Polish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Portuguese (Brazil))

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below.
Clock Dependencies: Product specific; see the links to product guides in the table below.
Last Updated: 25 Oct 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Portuguese)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Portuguese OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Office 2000 Professional  9.0   (Romanian)

Product Summary
Product: Office 2000 Professional Version: 9.0 Category:Compliant
Language: Romanian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Product specific; see the links to product guides in the table below
Clock Dependencies: Product specific; see the links to product guides in the table below
Last Updated: 18 Jul 1999
Product Details

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.

Product name and link to product guide

Summary of how product handles dates

Operational range for data

Compliance rating

Access 2000

Dates can be input and displayed in both predefined and custom formats via an input mask. Predefined formats include a short date format, which forces users to enter 2-digit dates. A custom format can be created to limit date entry to 4-digit years. If an input mask is not used (the default behavior), dates can be entered in 2- or 4-digit formats.

01/01/0100 through 12/31/9999

Compliant

Excel 2000

Dates are stored as numeric values and formatted according to one of several default formats, the most common being the system short date. If the system short date is a 2-digit format, even if the user enters a 4-digit year, it displays as two digits. To avoid this, users can change their system short date to a 4-digit format.

01/01/1900 through 12/31/9999

Compliant

Outlook 2000

Dates are stored and manipulated as full dates (for example, March 15, 2005) and are displayed in 2- and 4-digit formats according to the format selected by the user.

04/01/1601 through 08/31/4500

Compliant

PowerPoint 2000

Dates are stored and calculated in a 4-digit format.

System dependent

Compliant

Publisher 2000

Dates are entered as a field or as text and are displayed according to the format selected by the user. Individual date/time field data does not contain date/time values, only formats. The Calendar wizard allows entry of 4-digit years only.

System dependent

Compliant

Word 2000

Dates are stored as simple text strings or as a 32-bit integer. The date is represented by a 4-digit year. Dates saved with versions of documents retain their 4-digit year designations regardless of display.

01/01/1901 through 12/31/2411

Compliant

Small Business
Financial Tools

Dates that are displayed are obtained from the operating system date and time, stored as 4-digit year dates, and displayed according to the user settings in the operating system.

System dependent

Compliant

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the Short date style box, click a format that uses a 4-digit year ("yyyy").

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:

  1. On the Windows Start menu, point to Settings, and then click Control Panel.
  2. Double-click the Regional Settings icon, and then click the Date tab.
  3. In the When a 2-digit year is entered, interpret as a year between box, change the upper-limit year in the rightmost box.
    The lower-limit year automatically changes as the upper-limit changes.

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Itemized List of products in each Volume

YEAR 2000 READINESS DISCLOSURE

ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://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.