Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 2000 (English Australian)
| 01 Jan 1999 - 31 Dec 2035 | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| Operating System clock | ||
| 26 Aug 1999 | ||
|
This document applies to Encarta Encyclopedia Version: 2000; 2000 Deluxe; 2000 Deluxe (DVD) Release Date: 07/14/99 (2000 & 2000 Deluxe); US only: 08/18/99 (2000 Deluxe DVD) How the product handles dates: Encarta Encyclopedia does not accept user provided dates in its functionality with the following exception: Encarta Encyclopedia owners may download monthly Yearbook and Web Link updates for a period of 18 months, July 1999 through December 2000 for Encarta Encyclopedia 2000. Encarta Encyclopedia will automatically notify the user that a new update is available by checking to see if the Yearbook is up to date based on a regular publishing schedule. (New updates are made available on the Encarta Encyclopedia web site on a specific date each month during the 18-month life of the Yearbook (the 10th for US and the 15th for World English).) In the Troubleshooting section of the Downloads feature, Encarta Encyclopedia displays the Operating System Clock date, but it does not allow the user to change the date. The date format is as follows: MMMM DD YYYY (4-digit format). Operational ranges are as follows: Date display: through December 31, 2099 Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and have been tested through December 31, 2035. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 2000 (English British)
| 01 Jan 1999 - 31 Dec 2035 | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| Operating System clock | ||
| 26 Aug 1999 | ||
|
This document applies to Encarta Encyclopedia Version: 2000; 2000 Deluxe; 2000 Deluxe (DVD) Release Date: 07/14/99 (2000 & 2000 Deluxe); US only: 08/18/99 (2000 Deluxe DVD) How the product handles dates: Encarta Encyclopedia does not accept user provided dates in its functionality with the following exception: Encarta Encyclopedia owners may download monthly Yearbook and Web Link updates for a period of 18 months, July 1999 through December 2000 for Encarta Encyclopedia 2000. Encarta Encyclopedia will automatically notify the user that a new update is available by checking to see if the Yearbook is up to date based on a regular publishing schedule. (New updates are made available on the Encarta Encyclopedia web site on a specific date each month during the 18-month life of the Yearbook (the 10th for US and the 15th for World English).) In the Troubleshooting section of the Downloads feature, Encarta Encyclopedia displays the Operating System Clock date, but it does not allow the user to change the date. The date format is as follows: MMMM DD YYYY (4-digit format). Operational ranges are as follows: Date display: through December 31, 2099 Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and have been tested through December 31, 2035. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 2000 (French)
| 01 Jan 1999 - 31 Dec 2035 | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| Operating System Clock | ||
| 30 Aug 1999 | ||
|
This document applies to Encarta Encyclopedia Version: 2000; 2000 Deluxe; 2000 Deluxe (DVD) Release Date: 07/14/99 (2000 & 2000 Deluxe); US only: 08/18/99 (2000 Deluxe DVD) How the product handles dates: Encarta Encyclopedia does not accept user provided dates in its functionality with the following exception: Encarta Encyclopedia owners may download monthly Yearbook and Web Link updates for a period of 18 months, July 1999 through December 2000 for Encarta Encyclopedia 2000. Encarta Encyclopedia will automatically notify the user that a new update is available by checking to see if the Yearbook is up to date based on a regular publishing schedule. (New updates are made available on the Encarta Encyclopedia web site on a specific date each month during the 18-month life of the Yearbook (the 10th for US and the 15th for World English).) In the Troubleshooting section of the Downloads feature, Encarta Encyclopedia displays the Operating System Clock date, but it does not allow the user to change the date. The date format is as follows: MMMM DD YYYY (4-digit format). Operational ranges are as follows: Date display: through December 31, 2099 Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and have been tested through December 31, 2035. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 2000 (German)
| 01 Jan 1999 - 31 Dec 2035 | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| Operating System Clock | ||
| 30 Aug 1999 | ||
|
This document applies to Encarta Encyclopedia Version: 2000; 2000 Deluxe; 2000 Deluxe (DVD) Release Date: 07/14/99 (2000 & 2000 Deluxe); US only: 08/18/99 (2000 Deluxe DVD) How the product handles dates: Encarta Encyclopedia does not accept user provided dates in its functionality with the following exception: Encarta Encyclopedia owners may download monthly Yearbook and Web Link updates for a period of 18 months, July 1999 through December 2000 for Encarta Encyclopedia 2000. Encarta Encyclopedia will automatically notify the user that a new update is available by checking to see if the Yearbook is up to date based on a regular publishing schedule. (New updates are made available on the Encarta Encyclopedia web site on a specific date each month during the 18-month life of the Yearbook (the 10th for US and the 15th for World English).) In the Troubleshooting section of the Downloads feature, Encarta Encyclopedia displays the Operating System Clock date, but it does not allow the user to change the date. The date format is as follows: MMMM DD YYYY (4-digit format). Operational ranges are as follows: Date display: through December 31, 2099 Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and have been tested through December 31, 2035. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 2000 (Italian)
| 01 Jan 1999 - 31 Dec 2035 | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| Operating System Clock | ||
| 30 Aug 1999 | ||
|
This document applies to Encarta Encyclopedia Version: 2000; 2000 Deluxe; 2000 Deluxe (DVD) Release Date: 07/14/99 (2000 & 2000 Deluxe); US only: 08/18/99 (2000 Deluxe DVD) How the product handles dates: Encarta Encyclopedia does not accept user provided dates in its functionality with the following exception: Encarta Encyclopedia owners may download monthly Yearbook and Web Link updates for a period of 18 months, July 1999 through December 2000 for Encarta Encyclopedia 2000. Encarta Encyclopedia will automatically notify the user that a new update is available by checking to see if the Yearbook is up to date based on a regular publishing schedule. (New updates are made available on the Encarta Encyclopedia web site on a specific date each month during the 18-month life of the Yearbook (the 10th for US and the 15th for World English).) In the Troubleshooting section of the Downloads feature, Encarta Encyclopedia displays the Operating System Clock date, but it does not allow the user to change the date. The date format is as follows: MMMM DD YYYY (4-digit format). Operational ranges are as follows: Date display: through December 31, 2099 Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and have been tested through December 31, 2035. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 2000 (Japanese)
| 01 Jan 1999 - 31 Dec 2035 | ||
| NONE | ||
| NONE | ||
| System Clock | ||
| 20 Oct 1999 | ||
How the product handles dates: Encarta Encyclopedia does not accept user provided dates Encarta Encyclopedia owners may download monthly Yearbook and Web Link updates for a period of 18 months, starting July 1999 through December 2000 for Encarta Encyclopedia 2000. Encarta Encyclopedia will automatically notify the user that a new update is available by checking to see if the Yearbook is up to date based on a regular publishing schedule. (New updates are made available on the Encarta Encyclopedia web site on a specific date each month during the 18-month life of the Yearbook) In the Troubleshooting section of the Downloads feature, Encarta Encyclopedia displays the Operating System Clock date, but it does not allow the user to change the date. Operational ranges are as follows: Date display: through December 31, 2099 Encarta Encyclopedia uses a date to bring up a download and upgrade reminder window. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 2000 (Portuguese (Brazil))
| - | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| system clock | ||
| 13 Sep 1999 | ||
|
How the product handles dates: Encarta Encyclopedia does not handle dates or perform 2-digit shortcut interpretations. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 2000 (Spanish)
| 01 Jan 1999 - 31 Dec 2035 | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| Operating System Clock | ||
| 30 Aug 1999 | ||
|
This document applies to Encarta Encyclopedia Version: 2000; 2000 Deluxe; 2000 Deluxe (DVD) Release Date: 07/14/99 (2000 & 2000 Deluxe); US only: 08/18/99 (2000 Deluxe DVD) How the product handles dates: Encarta Encyclopedia does not accept user provided dates in its functionality with the following exception: Encarta Encyclopedia owners may download monthly Yearbook and Web Link updates for a period of 18 months, July 1999 through December 2000 for Encarta Encyclopedia 2000. Encarta Encyclopedia will automatically notify the user that a new update is available by checking to see if the Yearbook is up to date based on a regular publishing schedule. (New updates are made available on the Encarta Encyclopedia web site on a specific date each month during the 18-month life of the Yearbook (the 10th for US and the 15th for World English).) In the Troubleshooting section of the Downloads feature, Encarta Encyclopedia displays the Operating System Clock date, but it does not allow the user to change the date. The date format is as follows: MMMM DD YYYY (4-digit format). Operational ranges are as follows: Date display: through December 31, 2099 Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and have been tested through December 31, 2035. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 2000 (Swedish)
| 01 Jan 1999 - 31 Dec 2035 | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| Operating System Clock | ||
| 01 Oct 1999 | ||
|
This document applies to Encarta Encyclopedia Version: 2000; 2000 Deluxe; 2000 Deluxe (DVD) Release Date: 07/14/99 (2000 & 2000 Deluxe); US only: 08/18/99 (2000 Deluxe DVD) How the product handles dates: Encarta Encyclopedia does not accept user provided dates in its functionality with the following exception: Encarta Encyclopedia owners may download monthly Yearbook and Web Link updates for a period of 18 months, July 1999 through December 2000 for Encarta Encyclopedia 2000. Encarta Encyclopedia will automatically notify the user that a new update is available by checking to see if the Yearbook is up to date based on a regular publishing schedule. (New updates are made available on the Encarta Encyclopedia web site on a specific date each month during the 18-month life of the Yearbook (the 10th for US and the 15th for World English).) In the Troubleshooting section of the Downloads feature, Encarta Encyclopedia displays the Operating System Clock date, but it does not allow the user to change the date. The date format is as follows: MMMM DD YYYY (4-digit format). Operational ranges are as follows: Date display: through December 31, 2099 Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and have been tested through December 31, 2035. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 98 (Dutch)
| - | |||
| none | |||
| none | |||
| System Clock | |||
| 03 Nov 1998 | |||
|
| |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 98 (English)
| - | |||
| none | |||
| none | |||
| System clock | |||
| 28 Apr 1999 | |||
|
| |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 98 (English)
| - | ||
| NONE | ||
| Macintosh OS, QuickTime, QuickTime VR, Apple’s Text-To-Speech, MindVision InstallerVise (setup), AppleScript, Macromedia Flash | ||
| System Clock/Date & Time Control Panel | ||
| 27 Sep 1999 | ||
|
How the product handles dates:
Two-digit shortcut handling: Not Applicable Note: Operational Range for Data: Microsoft tested the product through December 31, 2019. Tests beyond this date were not possible due to limitations with the Apple Date & Time Control Panel. Dates set after 12/31/2019 roll back 100 years (dates set in 2020 will appear to be 1920). Information on Date & Time control panel limitations can be found at: http://www.apple.com/about/year2000/y2kos.html#osextensions | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 98 (French)
| - | |||
| none | |||
| none | |||
| System Clock | |||
| 03 Nov 1998 | |||
|
| |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 98 (German)
| - | |||
| none | |||
| none | |||
| System Clock | |||
| 03 Nov 1998 | |||
|
| |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 98 (Italian)
| - | |||
| none | |||
| none | |||
| System Clock | |||
| 03 Nov 1998 | |||
|
| |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 98 (Japanese)
| - | |||
| none | |||
| none | |||
| System Clock | |||
| 03 Nov 1998 | |||
|
| |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 98 (Spanish)
| - | |||
| none | |||
| none | |||
| System Clock | |||
| 03 Nov 1998 | |||
|
| |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (Dutch)
| - | ||
| none | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later, Internet Explorer 4.0x | ||
| System Clock | ||
| 08 Jun 1999 | ||
|
[This information applies to Encarta Encyclopedia 99, Encarta Encyclopedia 99 Deluxe, and Encarta Encyclopedia 99 Deluxe DVD.] How the product handles dates: Encarta Encyclopedia does not accept user-provided dates with the following exception: Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and function normally through December 31, 2035. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Encyclopedia Deluxe 99 has no date issues, however, its discs include the files for Internet Explorer v4.01 Service Pack 1 so that users have immediate access to browser software. The Microsoft Virtual Machine software update included with this version of Internet Explorer contains year 2000 issues. Encarta Encyclopedia does not use this component or Internet Explorer and is not affected by this matter. See the compliance document for Internet Explorer 4.0x for information to resolve its issues. Recommendations to meet compliance: Not Applicable | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (English)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later, Internet Explorer 4.0x | ||
| System clock | ||
| 31 Mar 1999 | ||
|
[This information applies to Encarta Encyclopedia 99, Encarta Encyclopedia 99 Deluxe, and Encarta Encyclopedia 99 Deluxe DVD.] How the product handles dates: Encarta Encyclopedia does not accept user-provided dates with the following exception: Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and function normally through December 31, 2035. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Encyclopedia Deluxe 99 has no date issues, however, its discs include the files for Internet Explorer v4.01 Service Pack 1 so that users have immediate access to browser software. The Microsoft Virtual Machine software update included with this version of Internet Explorer contains year 2000 issues. Encarta Encyclopedia does not use this component or Internet Explorer and is not affected by this matter. See the compliance document for Internet Explorer 4.0x for information to resolve its issues. Recommendations to meet compliance: Not Applicable | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (English Australian)
| - | ||
| none | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later, Internet Explorer 4.0x | ||
| System Clock | ||
| 08 Jun 1999 | ||
|
[This information applies to Encarta Encyclopedia 99, Encarta Encyclopedia 99 Deluxe, and Encarta Encyclopedia 99 Deluxe DVD.] How the product handles dates: Encarta Encyclopedia does not accept user-provided dates with the following exception: Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and function normally through December 31, 2035. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Encyclopedia Deluxe 99 has no date issues, however, its discs include the files for Internet Explorer v4.01 Service Pack 1 so that users have immediate access to browser software. The Microsoft Virtual Machine software update included with this version of Internet Explorer contains year 2000 issues. Encarta Encyclopedia does not use this component or Internet Explorer and is not affected by this matter. See the compliance document for Internet Explorer 4.0x for information to resolve its issues. Recommendations to meet compliance: Not Applicable | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (English British)
| - | ||
| none | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later, Internet Explorer 4.0x | ||
| System Clock | ||
| 08 Jun 1999 | ||
|
[This information applies to Encarta Encyclopedia 99, Encarta Encyclopedia 99 Deluxe, and Encarta Encyclopedia 99 Deluxe DVD.] How the product handles dates: Encarta Encyclopedia does not accept user-provided dates with the following exception: Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and function normally through December 31, 2035. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Encyclopedia Deluxe 99 has no date issues, however, its discs include the files for Internet Explorer v4.01 Service Pack 1 so that users have immediate access to browser software. The Microsoft Virtual Machine software update included with this version of Internet Explorer contains year 2000 issues. Encarta Encyclopedia does not use this component or Internet Explorer and is not affected by this matter. See the compliance document for Internet Explorer 4.0x for information to resolve its issues. Recommendations to meet compliance: Not Applicable | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (French)
| - | ||
| none | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later, Internet Explorer 4.0x | ||
| System Clock | ||
| 08 Jun 1999 | ||
|
[This information applies to Encarta Encyclopedia 99, Encarta Encyclopedia 99 Deluxe, and Encarta Encyclopedia 99 Deluxe DVD.] How the product handles dates: Encarta Encyclopedia does not accept user-provided dates with the following exception: Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and function normally through December 31, 2035. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Encyclopedia Deluxe 99 has no date issues, however, its discs include the files for Internet Explorer v4.01 Service Pack 1 so that users have immediate access to browser software. The Microsoft Virtual Machine software update included with this version of Internet Explorer contains year 2000 issues. Encarta Encyclopedia does not use this component or Internet Explorer and is not affected by this matter. See the compliance document for Internet Explorer 4.0x for information to resolve its issues. Recommendations to meet compliance: Not Applicable | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (German)
| - | ||
| none | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later, Internet Explorer 4.0x | ||
| System Clock | ||
| 08 Jun 1999 | ||
|
[This information applies to Encarta Encyclopedia 99, Encarta Encyclopedia 99 Deluxe, and Encarta Encyclopedia 99 Deluxe DVD.] How the product handles dates: Encarta Encyclopedia does not accept user-provided dates with the following exception: Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and function normally through December 31, 2035. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Encyclopedia Deluxe 99 has no date issues, however, its discs include the files for Internet Explorer v4.01 Service Pack 1 so that users have immediate access to browser software. The Microsoft Virtual Machine software update included with this version of Internet Explorer contains year 2000 issues. Encarta Encyclopedia does not use this component or Internet Explorer and is not affected by this matter. See the compliance document for Internet Explorer 4.0x for information to resolve its issues. Recommendations to meet compliance: Not Applicable | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (Italian)
| - | ||
| none | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later, Internet Explorer 4.0x | ||
| System Clock | ||
| 08 Jun 1999 | ||
|
[This information applies to Encarta Encyclopedia 99, Encarta Encyclopedia 99 Deluxe, and Encarta Encyclopedia 99 Deluxe DVD.] How the product handles dates: Encarta Encyclopedia does not accept user-provided dates with the following exception: Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and function normally through December 31, 2035. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Encyclopedia Deluxe 99 has no date issues, however, its discs include the files for Internet Explorer v4.01 Service Pack 1 so that users have immediate access to browser software. The Microsoft Virtual Machine software update included with this version of Internet Explorer contains year 2000 issues. Encarta Encyclopedia does not use this component or Internet Explorer and is not affected by this matter. See the compliance document for Internet Explorer 4.0x for information to resolve its issues. Recommendations to meet compliance: Not Applicable | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (Japanese)
| - | ||||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||||
| System clock | ||||
| 22 Jun 1999 | ||||
| ||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (Portuguese (Brazil))
| - | ||
| none | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later, Internet Explorer 4.0x | ||
| System Clock | ||
| 08 Jun 1999 | ||
|
[This information applies to Encarta Encyclopedia 99, Encarta Encyclopedia 99 Deluxe, and Encarta Encyclopedia 99 Deluxe DVD.] How the product handles dates: Encarta Encyclopedia does not accept user-provided dates with the following exception: Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and function normally through December 31, 2035. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Encyclopedia Deluxe 99 has no date issues, however, its discs include the files for Internet Explorer v4.01 Service Pack 1 so that users have immediate access to browser software. The Microsoft Virtual Machine software update included with this version of Internet Explorer contains year 2000 issues. Encarta Encyclopedia does not use this component or Internet Explorer and is not affected by this matter. See the compliance document for Internet Explorer 4.0x for information to resolve its issues. Recommendations to meet compliance: Not Applicable | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Encyclopedia 99 (Spanish)
| - | ||
| none | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later, Internet Explorer 4.0x | ||
| System Clock | ||
| 08 Jun 1999 | ||
|
[This information applies to Encarta Encyclopedia 99, Encarta Encyclopedia 99 Deluxe, and Encarta Encyclopedia 99 Deluxe DVD.] How the product handles dates: Encarta Encyclopedia does not accept user-provided dates with the following exception: Encarta Encyclopedia also uses a date to bring up download and upgrade reminder windows. These are based off of set dates and function normally through December 31, 2035. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Encyclopedia Deluxe 99 has no date issues, however, its discs include the files for Internet Explorer v4.01 Service Pack 1 so that users have immediate access to browser software. The Microsoft Virtual Machine software update included with this version of Internet Explorer contains year 2000 issues. Encarta Encyclopedia does not use this component or Internet Explorer and is not affected by this matter. See the compliance document for Internet Explorer 4.0x for information to resolve its issues. Recommendations to meet compliance: Not Applicable | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Eng. Learning 1.0 (French)
| 23 Feb 1999 - 01 Jan 2035 | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, SpeechSDK (SAPI), DirectX, Direct Media, Microsoft Foundation Classes, AudioMan, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 22 Jun 1999 | ||
|
Encarta Interactive English Learning How the product handles dates: The Study Planner is the feature in Encarta Interactive English Learning that uses dates. The user picks the days of the week he/she wants to work and either chooses a length of time to study each day or picks an end date using a calendar control. The Study Planner then calculates the unknown variable to determine the user’s study plan. The dates that are calculated and displayed in Encarta Interactive English Learning use a four-digit year. Two-digit shortcut handling: Not Applicable. What issues are there? Encarta Interactive English Learning uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. However, Encarta Interactive English Learning does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta Interactive English Learning, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. The posted Internet Explorer 4.01 Service Pack 1 issues do not affect Encarta Interactive English Learning.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Eng. Learning 1.0 (Italian)
| 15 Jun 1999 - 01 Jan 2035 | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, SpeechSDK (SAPI), DirectX, Direct Media, Microsoft Foundation Classes, AudioMan, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 22 Jun 1999 | ||
|
Encarta Interactive English Learning How the product handles dates: The Study Planner is the feature in Encarta Interactive English Learning that uses dates. The user picks the days of the week he/she wants to work and either chooses a length of time to study each day or picks an end date using a calendar control. The Study Planner then calculates the unknown variable to determine the user’s study plan. The dates that are calculated and displayed in Encarta Interactive English Learning use a four-digit year. Two-digit shortcut handling: Not Applicable. What issues are there? Encarta Interactive English Learning uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. However, Encarta Interactive English Learning does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta Interactive English Learning, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. The posted Internet Explorer 4.01 Service Pack 1 issues do not affect Encarta Interactive English Learning.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Eng. Learning 1.0 (Japanese)
| 23 Feb 1999 - 01 Jan 2035 | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, SpeechSDK (SAPI), DirectX, Direct Media, Microsoft Foundation Classes, AudioMan, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 22 Jun 1999 | ||
|
Encarta Interactive English Learning How the product handles dates: The Study Planner is the feature in Encarta Interactive English Learning that uses dates. The user picks the days of the week he/she wants to work and either chooses a length of time to study each day or picks an end date using a calendar control. The Study Planner then calculates the unknown variable to determine the user’s study plan. The dates that are calculated and displayed in Encarta Interactive English Learning use a four-digit year. Two-digit shortcut handling: Not Applicable. What issues are there? Encarta Interactive English Learning uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. However, Encarta Interactive English Learning does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta Interactive English Learning, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. The posted Internet Explorer 4.01 Service Pack 1 issues do not affect Encarta Interactive English Learning.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Eng. Learning 1.0 (Polish)
| - | ||
| NONE | ||
| Internet Explorer 5.0, SpeechSDK (SAPI), DirectX, Direct Media, Microsoft Foundation Classes, AudioMan, Windows 95, Windows 98, Windows NT4 with Service Pack 3 or later | ||
| System Clock | ||
| 20 Oct 1999 | ||
How the product handles dates: The Study Planner is the feature in Encarta Interactive English Learning that uses dates. The user picks the days of the week he/she wants to work and either chooses a length of time to study each day or picks an end date using a calendar control. The Study Planner then calculates the user’s study plan. The dates that are calculated and displayed in Encarta Interactive English Learning use a four-digit year. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer 5.0 installs with Encarta Interactive English Learning, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Eng. Learning 1.0 (Spanish)
| 15 Apr 1999 - 01 Jan 2035 | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, SpeechSDK (SAPI), DirectX, Direct Media, Microsoft Foundation Classes, AudioMan, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 22 Jun 1999 | ||
|
Encarta Interactive English Learning How the product handles dates: The Study Planner is the feature in Encarta Interactive English Learning that uses dates. The user picks the days of the week he/she wants to work and either chooses a length of time to study each day or picks an end date using a calendar control. The Study Planner then calculates the unknown variable to determine the user’s study plan. The dates that are calculated and displayed in Encarta Interactive English Learning use a four-digit year. Two-digit shortcut handling: Not Applicable. What issues are there? Encarta Interactive English Learning uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. However, Encarta Interactive English Learning does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta Interactive English Learning, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. The posted Internet Explorer 4.01 Service Pack 1 issues do not affect Encarta Interactive English Learning.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Interactive World Atlas 2000 (5.0) (Dutch)
| - | ||
| None | ||
| Internet Explorer 5.0, Windows 95, Windows 98, Windows NT4 with Service Pack 3 | ||
| System Clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: There are two features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, some other statistics have projections for the next several years. No issues have been identified with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer installs with Encarta Interactive World Atlas 2000, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Interactive World Atlas 2000 (5.0) (English)
| - | ||
| None | ||
| Internet Explorer 5.0, Windows 95, Windows 98, Windows NT4 with Service Pack 3 | ||
| System Clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: There are two features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, some other statistics have projections for the next several years. No issues have been identified with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer installs with Encarta Interactive World Atlas 2000, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Interactive World Atlas 2000 (5.0) (English British)
| - | ||
| None | ||
| Internet Explorer 5.0, Windows 95, Windows 98, Windows NT4 with Service Pack 3 | ||
| System Clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: There are two features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, some other statistics have projections for the next several years. No issues have been identified with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer installs with Encarta Interactive World Atlas 2000, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Interactive World Atlas 2000 (5.0) (French)
| - | ||
| None | ||
| Internet Explorer 5.0, Windows 95, Windows 98, Windows NT4 with Service Pack 3 | ||
| System Clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: There are two features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, some other statistics have projections for the next several years. No issues have been identified with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer installs with Encarta Interactive World Atlas 2000, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Interactive World Atlas 2000 (5.0) (German)
| - | ||
| None | ||
| Internet Explorer 5.0, Windows 95, Windows 98, Windows NT4 with Service Pack 3 | ||
| System Clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: There are two features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, some other statistics have projections for the next several years. No issues have been identified with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer installs with Encarta Interactive World Atlas 2000, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Interactive World Atlas 2000 (5.0) (Italian)
| - | ||
| None | ||
| Internet Explorer 5.0, Windows 95, Windows 98, Windows NT4 with Service Pack 3 | ||
| System Clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: There are two features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, some other statistics have projections for the next several years. No issues have been identified with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer installs with Encarta Interactive World Atlas 2000, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Interactive World Atlas 2000 (5.0) (Japanese)
| 01 Jan 1999 - 31 Dec 2035 | ||
| NONE | ||
| NONE | ||
| System Clock | ||
| 20 Oct 1999 | ||
How the product handles dates: There are two features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, some other statistics have projections for the next several years. No issues have been identified with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer installs with Encarta Interactive World Atlas 2000, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Interactive World Atlas 2000 (5.0) (Portuguese (Brazil))
| - | ||
| None | ||
| Internet Explorer 5.0, Windows 95, Windows 98, Windows NT4 with Service Pack 3 | ||
| System Clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: There are two features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, some other statistics have projections for the next several years. No issues have been identified with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer installs with Encarta Interactive World Atlas 2000, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Interactive World Atlas 2000 (5.0) (Spanish)
| - | ||
| None | ||
| Internet Explorer 5.0, Windows 95, Windows 98, Windows NT4 with Service Pack 3 | ||
| System Clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: There are two features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, some other statistics have projections for the next several years. No issues have been identified with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable Recommendations to meet compliance: Since Internet Explorer installs with Encarta Interactive World Atlas 2000, Microsoft recommends reviewing the Internet Explorer 5.0 compliance document for any necessary year 2000 actions.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Online RTW 8/2/1999 (English)
| - | ||
| None | ||
| Internet Explorer on MS Windows: MS Media Player 6.0 or later. Netscape on MS Windows: Quicktime 3.0 or later. Internet Explorer on Mac: Quicktime 3.0 or later. Netscape on Mac: Quicktime 3.0 or later | ||
| None | ||
| 14 Oct 1999 | ||
|
Encarta
Online can be found at: http://www.encarta.msn.com/ How the product handles dates: Microsoft Encarta Online,
is an online Encyclopedia, that is made available to users over the World Wide
Web. Content is read-only and is stored on Microsoft Web Servers. Users are not
required to input date-related data. The only date related components to test
are Online Billing (which is provided by an external component called OneBill),
the Automatic content update process (an automatic process used to update the
encyclopedia content) and correct expiration of Free Trial and Volume Licensing
Accounts. Where the product handles
dates: ·
Credit card
information is obtained from the user using the OneBill component. This is
where Encarta.msn.com asks the user for date
data. ·
The automatic content
update mechanism uses Operating System APIs to get and compare file-stamps. ·
The Free Trial
component uses MS SQL Server 7.0 data fields to store free trial account
creation and expiration dates. Two-digit shortcut handling: The product does not use
2-digit shortcuts. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 2000 (Canadian English)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 | ||
| System Clock | ||
| 14 Oct 1999 | ||
|
Release Date: 7/14/99 (CD) 8/18/99 (DVD US) 8/20/99 (DVD International English) How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite 2000: Encarta Encyclopedia 2000Encarta Interactive World Atlas 2000 Encarta World English Dictionary There are no known issues in the suite code. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 2000 (English)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 | ||
| System Clock | ||
| 14 Oct 1999 | ||
|
Release Date: 7/14/99 (CD) 8/18/99 (DVD US) 8/20/99 (DVD International English) How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite 2000: Encarta Encyclopedia 2000Encarta Interactive World Atlas 2000 Encarta World English Dictionary There are no known issues in the suite code. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 2000 (English Australian)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 | ||
| System Clock | ||
| 14 Oct 1999 | ||
|
Release Date: 7/14/99 (CD) 8/18/99 (DVD US) 8/20/99 (DVD International English) How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite 2000: Encarta Encyclopedia 2000Encarta Interactive World Atlas 2000 Encarta World English Dictionary There are no known issues in the suite code. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 2000 (English British)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 | ||
| System Clock | ||
| 14 Oct 1999 | ||
|
Release Date: 7/14/99 (CD) 8/18/99 (DVD US) 8/20/99 (DVD International English) How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite 2000: Encarta Encyclopedia 2000Encarta Interactive World Atlas 2000 Encarta World English Dictionary There are no known issues in the suite code. Two-digit shortcut handling: Not Applicable.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 2000 (French)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| system clock | ||
| 14 Oct 1999 | ||
|
How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite: Encarta Encyclopedia 2000 Encarta Interactive World Atlas 2000There are no known issues in the suite code itself .Two-digit shortcut handling: This product does not perform two-digit shortcut interpretations
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 2000 (Italian)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| system clock | ||
| 14 Oct 1999 | ||
|
How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite: Encarta Encyclopedia 2000 Encarta Interactive World Atlas 2000There are no known issues in the suite code itself .Two-digit shortcut handling: This product does not perform two-digit shortcut interpretations
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 2000 (Japanese)
| 01 Jan 1999 - 31 Dec 2035 | ||
| NONE | ||
| NONE | ||
| System Clock | ||
| 21 Oct 1999 | ||
How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite 2000: Encarta Interactive World Atlas 2000 Bookshelf 2.0 for Encarta Reference Suite There are no known issues year 2000 in the suite code. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 2000 (Spanish)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 or later | ||
| system clock | ||
| 14 Oct 1999 | ||
|
How the product handles dates: Microsoft Bookshelf en Español does not accept user-provided dates for functionality. Please see compliance statements for each of the additional products included in Encarta Reference Suite: Encarta Encyclopedia 2000 Encarta Interactive World Atlas 2000There are no known issues in the suite code itself .Two-digit shortcut handling: This product does not perform 2-digit shortcut interpretations
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 98 (English)
| - | ||||
| NONE | ||||
| NONE | ||||
| System Clock | ||||
| 14 Oct 1999 | ||||
| Description of how the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite: | ||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 99 (English)
| - | ||||
| None | ||||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 | ||||
| System clock | ||||
| 14 Oct 1999 | ||||
|
[This information applies to Encarta Reference Suite 99 and Encarta Reference Suite 99 DVD.] How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite:
Two-digit shortcut handling: Not Applicable What issues are there?: Not Applicable Recommendations to meet compliance: Not Applicable
| ||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 99 (English Australian)
| - | ||||
| none | ||||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 | ||||
| System Clock | ||||
| 14 Oct 1999 | ||||
|
[This information applies to Encarta Reference Suite 99 and Encarta Reference Suite 99 DVD.] How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite:
Two-digit shortcut handling: Not Applicable What issues are there?: Not Applicable Recommendations to meet compliance: Not Applicable
| ||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 99 (English British)
| - | ||||
| none | ||||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 | ||||
| System Clock | ||||
| 14 Oct 1999 | ||||
|
[This information applies to Encarta Reference Suite 99 and Encarta Reference Suite 99 DVD.] How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite:
Two-digit shortcut handling: Not Applicable What issues are there?: Not Applicable Recommendations to meet compliance: Not Applicable
| ||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 99 (Japanese)
| - | ||||
| none | ||||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 | ||||
| System Clock | ||||
| 14 Oct 1999 | ||||
|
[This information applies to Encarta Reference Suite 99 and Encarta Reference Suite 99 DVD.] How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite:
Two-digit shortcut handling: Not Applicable What issues are there?: Not Applicable Recommendations to meet compliance: Not Applicable
| ||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Reference Suite 99 (Spanish)
| - | ||||
| none | ||||
| Windows 95, Windows 98, Windows NT 4 Service Pack 3 | ||||
| System Clock | ||||
| 14 Oct 1999 | ||||
|
[This information applies to Encarta Reference Suite 99 and Encarta Reference Suite 99 DVD.] How the product handles dates: Please see compliance statements for each of the individual products included in Encarta Reference Suite:
Two-digit shortcut handling: Not Applicable What issues are there?: Not Applicable Recommendations to meet compliance: Not Applicable
| ||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Virtual Globe 1999 4.0 (English)
| - | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, Windows 95, Windows 98, Windows NT4 with Service Pack 3 | ||
| System Clock | ||
| 12 Apr 1999 | ||
|
How the product handles dates: There are only a few features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, a couple of statistics have projections for the next several years. They work appropriately with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta Virtual Globe 1999 uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. Encarta Virtual Globe 1999 does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta Virtual Globe 1999, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. Again, this matter does not affect Encarta Virtual Globe 1999.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta Virtual Globe 98 (English)
| - | ||
| NONE | ||
| NONE | ||
| System Clock | ||
| 07 Jul 1999 | ||
| Operational Range for Data: N/A (tested through December 31, 2035) Description of how the product handles dates: Encarta Virtual Globe does not accept user-provided dates for any functionality. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta World Atlas 1999 4.0 (English)
| - | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 30 Aug 1999 | ||
|
How the product handles dates: There are only a few features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, a couple of statistics have projections for the next several years. They work appropriately with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta World Atlas 1999 uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. Encarta World Atlas 1999 does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta World Atlas 1999, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. Again, this matter does not affect Encarta World Atlas 1999.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta World Atlas 1999 4.0 (French)
| - | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 30 Aug 1999 | ||
|
How the product handles dates: There are only a few features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, a couple of statistics have projections for the next several years. They work appropriately with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta World Atlas 1999 uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. Encarta World Atlas 1999 does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta World Atlas 1999, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. Again, this matter does not affect Encarta World Atlas 1999.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta World Atlas 1999 4.0 (German)
| - | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 30 Aug 1999 | ||
|
How the product handles dates: There are only a few features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, a couple of statistics have projections for the next several years. They work appropriately with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta World Atlas 1999 uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. Encarta World Atlas 1999 does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta World Atlas 1999, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. Again, this matter does not affect Encarta World Atlas 1999.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta World Atlas 1999 4.0 (Italian)
| - | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 30 Aug 1999 | ||
|
How the product handles dates: There are only a few features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, a couple of statistics have projections for the next several years. They work appropriately with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta World Atlas 1999 uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. Encarta World Atlas 1999 does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta World Atlas 1999, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. Again, this matter does not affect Encarta World Atlas 1999.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta World Atlas 1999 4.0 (Japanese)
| - | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 30 Aug 1999 | ||
|
How the product handles dates: There are only a few features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, a couple of statistics have projections for the next several years. They work appropriately with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta World Atlas 1999 uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. Encarta World Atlas 1999 does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta World Atlas 1999, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. Again, this matter does not affect Encarta World Atlas 1999.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta World Atlas 1999 4.0 (Spanish)
| - | ||
| None | ||
| Internet Explorer 4.01 Service Pack 1, Windows 95, Windows 98, Windows NT4 (Service Pack 3) or later | ||
| System Clock | ||
| 30 Aug 1999 | ||
|
How the product handles dates: There are only a few features that use dates. The statistics feature has a date field for the particular statistic. It uses a 4-digit year. Also, a couple of statistics have projections for the next several years. They work appropriately with projection dates after the year 2000. Two-digit shortcut handling: Not Applicable What issues are there?: Encarta World Atlas 1999 uses Internet Explorer 4.01 Service Pack 1 to render the content of the application. Internet Explorer has identified a year 2000 issue with a component of Internet Explorer. Encarta World Atlas 1999 does not use this component within the application and is not affected by this matter. Recommendations: Since Internet Explorer installs with Encarta World Atlas 1999, Microsoft recommends reviewing the Internet Explorer 4.01 compliance document for necessary year 2000 actions, if customers are interested in applying these updates. Again, this matter does not affect Encarta World Atlas 1999.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta World Eng. Dictionary (English)
| 01 Jan 1999 - 01 Jan 2050 | ||
| None | ||
| Operating System | ||
| System clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: Encarta World English Dictionary does not accept user-provided dates. Encarta World English Dictionary does use the system date to check if a day has passed since last time the program was used to determine if a new "Of the Day" article should be displayed. The "Of the Day" article list is a rotating limited set. Two-digit shortcut handling: Not applicable.
Testing guidelines and recommendations: Verify the "Of the Day article" changes when the clock is changed and the product is reopened.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta World Eng. Dictionary (English Australian)
| 01 Jan 1999 - 01 Jan 2050 | ||
| None | ||
| Operating System | ||
| System clock | ||
| 26 Aug 1999 | ||
|
How the product handles dates: Encarta World English Dictionary does not accept user-provided dates. Encarta World English Dictionary does use the system date to check if a day has passed since last time the program was used to determine if a new "Of the Day" article should be displayed. The "Of the Day" article list is a rotating limited set. Two-digit shortcut handling: Not applicable.
Testing guidelines and recommendations: Verify the "Of the Day article" changes when the clock is changed and the product is reopened.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Encarta World Eng. Dictionary (English British)
| 01 Jan 1999 - 01 Jan 2050 | ||
| None | ||
| Operating System | ||
| System Clock | ||
| 02 Sep 1999 | ||
|
How the product handles dates: Encarta World English Dictionary does not accept user-provided dates. Encarta World English Dictionary does use the system date to check if a day has passed since last time the program was used to determine if a new "Of the Day" article should be displayed. The "Of the Day" article list is a rotating limited set. Two-digit shortcut handling: Not applicable.
Testing guidelines and recommendations: Verify the "Of the Day article" changes when the clock is changed and the product is reopened.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Entertainment Pack 1.0 (English)
| - | ||
| None | ||
| None | ||
| None | ||
| 20 Jul 1999 | ||
|
Best of Windows Entertainment Pack Best of Windows Entertainment Pack does not handle dates or perform two-digit shortcut interpretations. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Entertainment Pack for Windows CE 2.0 (English)
| - | ||||
| None | ||||
| None | ||||
| None | ||||
| 04 Oct 1999 | ||||
|
| ||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Canadian French)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Apple operating System | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Danish)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Apple Operating System | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Dutch)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Apple Operating System | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (English)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Mac operating system | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Finnish)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Mac operating system | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (French)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Mac operating system | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (German)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Mac operating system | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Italian)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Mac operating system | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Japanese)
| 01 Jan 1904 - 31 Dec 2078 | |||||||||||||||||||||||
| None | |||||||||||||||||||||||
| Mac operating system | |||||||||||||||||||||||
| System clock | |||||||||||||||||||||||
| 22 Sep 1999 | |||||||||||||||||||||||
|
How the product handles dates:
Leap Year. Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base (KB) article Q181370 for more information.)Two-digit shortcut handling: See discussion above. (See Knowledge Base article Q164406 for more information.)Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel 5 might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1-1-15". When you paste "1-1-15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an interpretation can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See Knowledge Base article Q182766 for more information.)
Recording date entry in a macro records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See Knowledge Base article Q182766 for more information.)Using a format such as "Dec 98" will not be interpreted at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel 5 assumes it is a year. However, Microsoft Excel 5 assumes "Dec 01" refers to December 1 of the current year. (See Knowledge Base article Q180952 for more information.)
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files. The following areas should be examined to verify dates are being properly used. The table below can be used to guide testing of Microsoft Excel 5 within your organization.
Additional Testing Instructions Microsoft provides the following Year 2000 testing guidelines for Microsoft Excel 5.
Note: The year 1900 is not a leap year. However, in your testing you may notice that Microsoft Excel 5 treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.) | |||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Norwegian)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Mac operating system | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Portuguese)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Mac operating system | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Spanish)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Mac operating system | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 5.0 (Swedish)
| 01 Jan 1904 - 31 Dec 2078 | ||
| None | ||
| Mac operating system | ||
| System clock | ||
| 22 Sep 1999 | ||
|
How the product handles dates: Storage: Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. . Excel 5 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526th day in the century. Formatting: When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (2-digit year), then even when the user types a YYYY date (4-digit year), it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry: If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown Leap Year: Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)Two-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1920 through 2019. (See Knowledge Base (KB) article Q164406 for more information.)What are the acceptable deviations? MS Query accepts two-digit year date formatting for your ODBC query, but will always assume a twentieth century date. To avoid this issue, you should always use four digit years for queries based upon date data. Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Microsoft Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Microsoft Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q182766 for more information.)
The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015.
Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q182766 for more information.)
Using a format such as "Dec 98" will not function correctly at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)
Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2-digit year format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Microsoft Excel within your organization. Sub-system Component File Various File Formats Avoid storing 2Y dates in text file formats such as TXT, DIF, CSV, PRN. The default column width with default fonts may truncate characters with date formats that have 8 digits and two separators. To correct, increase the column width, or change the font to a fixed-width typeface such as Courier New. Data Import from: text, Databases, External data sources Sort Data imported from databases and other external sources is often imported as text. Importing 2-digit years will be parsed with the 2019/1920 cutoff. This is different from later versions of Excel, so use 4-digit years to prevent confusion. Basic Use Functions Date Entry Natural Language Functions Functions referring to text dates will parse according to the 2019/1920 cutoff rule. Date entry will parse according to the 2019/1920 cutoff rule. Visual Data Charts Since chart labels are normally used for display, and not for calculation, this shouldn't pose much of an issue. VB/VBA Transfer between VB/VBA and cells Internally, VBA treats dates as serial values, exactly like Excel. However, since VBA uses the "M/d/yy" format, you should avoid transferring the date text through VBA, since it could parse to the wrong century. This will also help avoid issues with international users who have a system short date format with an order other than M-d-y. Additional Testing Instructions: Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Excel. Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy".
Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test.
Set the system clock to 11:59 p.m. December 31, 1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Verify that Excel recognizes the year 2000 as a leap year: Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.)
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 98 (English)
| 01 Jan 1904 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | ||||||||||||||||||||
| Operating system clock | ||||||||||||||||||||
| 22 Sep 1999 | ||||||||||||||||||||
|
Description of how the product handles dates:
2-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. Common date usage errors:
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel 98: For more information and download of these tools see Knowledge Base article Q193344.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Excel within your organization.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 98 (French)
| 01 Jan 1904 - 31 Dec 9999 | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | ||||||||||||||||||||
| Operating system clock | ||||||||||||||||||||
| 01 Oct 1999 | ||||||||||||||||||||
|
Description of how the product handles dates:
2-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. Common date usage errors:
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel 98: For more information and download of these tools see Knowledge Base article Q193344.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Excel within your organization.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 98 (German)
| 01 Jan 1904 - 31 Dec 9999 | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | ||||||||||||||||||||
| Operating system clock | ||||||||||||||||||||
| 01 Oct 1999 | ||||||||||||||||||||
|
Description of how the product handles dates:
2-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. Common date usage errors:
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel 98: For more information and download of these tools see Knowledge Base article Q193344.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Excel within your organization.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 98 (Italian)
| 01 Jan 1904 - 31 Dec 9999 | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | ||||||||||||||||||||
| Operating system clock | ||||||||||||||||||||
| 01 Oct 1999 | ||||||||||||||||||||
|
Description of how the product handles dates:
2-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. Common date usage errors:
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel 98: For more information and download of these tools see Knowledge Base article Q193344.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Excel within your organization.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 98 (Japanese)
| 01 Jan 1904 - 31 Dec 9999 | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | ||||||||||||||||||||
| Operating system clock | ||||||||||||||||||||
| 01 Oct 1999 | ||||||||||||||||||||
|
Description of how the product handles dates:
2-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. Common date usage errors:
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel 98: For more information and download of these tools see Knowledge Base article Q193344.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Excel within your organization.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 98 (Spanish)
| 01 Jan 1904 - 31 Dec 9999 | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | ||||||||||||||||||||
| Operating system clock | ||||||||||||||||||||
| 01 Oct 1999 | ||||||||||||||||||||
|
Description of how the product handles dates:
2-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. Common date usage errors:
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel 98: For more information and download of these tools see Knowledge Base article Q193344.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Excel within your organization.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel (Macintosh) 98 (Swedish)
| 01 Jan 1904 - 31 Dec 9999 | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | ||||||||||||||||||||
| Operating system clock | ||||||||||||||||||||
| 01 Oct 1999 | ||||||||||||||||||||
|
Description of how the product handles dates:
2-digit shortcut handling: See discussion above. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. Common date usage errors:
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel 98: For more information and download of these tools see Knowledge Base article Q193344.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Excel within your organization.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (Arabic)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (Basque)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (Chinese - Simplified)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (Chinese - Traditional)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (Croatian)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (Czech)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (Danish)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (Dutch)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (English)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (English Australian)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 2000 9.0 (English British)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| None | ||||||||||||||||||||
| Windows 95 or Windows 98, Windows NT 4 with Service Pack 3 or greater, or Windows NT 5 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 09 Nov 1999 | ||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Excel 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.How the product handles dates:
The following optional registry setting can also be used to keep a "yyyy" format when a 4-digit date is entered: HKEY_CURRENT_USER\Software\ Microsoft\Office\9.0\Excel\Options::EnableFourDigitYearDisplay(DWORD)=1. This setting only affects dates entered with 4-digit years: that is, entering "1/1/1925" will display "1/1/1925," but entering "1/1/25" will still display "1/1/25."
Because this is a system-wide setting, it will affect all programs that call the application programming interface (API); however, it will only affect older programs, such as Microsoft Access 97, which use OLE automation to determine dates. Also, 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. For more information, see the
Two-digit shortcut handling : See "Parsing on Date Entry" above.Common date usage errors:
Microsoft has created the following add-in tools to help users identify Year 2000 issues and solutions in Excel 97 and later versions:
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The following table can be used to guide testing of Excel 2000 within your organization.
Additional testing instructions: Excel 2000 has been designed for calculations well beyond the year 2000. Microsoft understands that, for various reasons, customers may be required to conduct their own Year 2000 certification testing. The following tests may aid customers in their own certification of Excel. Excel is designed to handle 2-digit year shortcuts well into the next century. Dates are stored internally, in a complete form, with full century information. Nevertheless, a user or administrator may elect to change the operating system short date format to a 4-digit display in order to avoid ambiguity when reading or transferring dates. Note that this change can affect column widths and print layout and it could require additional changes in your worksheets. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Custom on the Number tab (Format menu, Cells command) in Excel, and then entering a 4-digit year format.To change the system short date format, do the following: On the Windows Start menu, point to Settings, click Control Panel, double-click the Regional Settings icon, and then click the Date tab. In the Short date style list, click a format that includes a 4-digit year ("yyyy"). Because Excel 2000 Beta 2 is a beta product, it has an expiration date; however, 2 time periods exist to allow users to verify that Excel is Year 2000 compliant. These periods are 12/15/1999 to 03/15/2000 and 12/15/2000 to 03/15/2001.
Set the system clock to 11:58 P.M., 12/31/1999. Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After 2 minutes, press the F9 key to recalculate the formula that you entered in A1. Note that the time and date shown are in the year 2000 and that nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test.
Start Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, which indicates that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year; however, in your testing, you may notice that Excel treats 1900 as if it is. This algorithm is by design and was adopted to maintain compatibility with dates in Lotus 1-2-3. The calculation for leap years that is used by the Gregorian calendar is as follows: If a year is evenly divisible by four, it is a leap year unless it is also evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year unless it is also evenly divisible by 400. (See Excel 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find, and file I/O. For additional information that is appropriate for Excel 2000 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Itemized List of products in each Volume
|
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA. ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
||
|
Wednesday, November 17, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act.  | ||