Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Polish)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| Office 97 Service Release 2 | ||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 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 Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Download the Office 97 SR2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates. VB/VBA uses the same serial date system, with the exception of 1-JAN-1900 through 28-FEB-1900, where the values are different by 1, as a result of a backward-compatibility issue for a bug in Lotus 1-2-3 that treats 1900 as a leap year. Previous versions of Excel recognize 01-JAN-1900 through 31-DEC-2078 as valid dates. 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, then even when the user types a YYYY date, it will by default display in a YY format. To avoid this, the default format can be changed to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 30 is 20XX, and equal to or greater than 30 is 19XX. So, for instance, "1/1/25" used to parse to 01-JAN-1925, but now parses to 01-JAN-2025. Suggest displaying dates in a YYYY format so the century is clearly shown. String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above. This may be a concern to some users because a formula such as =YEAR("1/1/25") returned 1925 in previous versions, but in Excel97 returns 2025. Note that this only happens when "1/1/25" is a string using a 2-digit year format. Also, the Date Migration Wizard, an Excel add-in, is available to aid the user in identifying and correcting these situations. See below for more information and a link to the Date Migration Wizard.
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: 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 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 KB articles Q180159 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. Using a format such as "Dec 98" or "12/98" will not function correctly in 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, Microsoft 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.)An undocumented behavior of Microsoft Query (all versions) may unintentionally encourage some users to enter a date criterion by specifying merely a month and day (such as "12/25"). In that instance, Query interprets the date as month and day of the current year. When the current year is equal to or greater than 2000, a malformed SQL statement is generated. In the event that this occurs, an error is generated and no data is returned. Avoiding this error is readily accomplished by entering a full and complete date. Microsoft recommends that all dates be entered in unambiguous formats, including a 4-digit year, but current versions of Microsoft Query also support windowing of 2-digit year dates as described in the Excel Year 2000 Product Guides. Due to the ambiguous nature of text dates, in general they will always have 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 Microsoft 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 not 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 or concern because users who use a date format with an order other than M-d-y will experience interpretive miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned concerns.
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel97: The Date Migration Wizard is designed to help users find instances where date-related arguments are referencing text dates that only specify the last two digits of a year. This can cause changes in calculation from previous versions of Microsoft Excel. For more information see Knowledge Base article Q176943.The Date Fix Wizard helps users find errors where the wrong century was entered for a date. It also allows the user to change date formats in a workbook to formats that display four digits of the year. Finally, it allows the user to scan workbooks for the earliest and latest dates in workbooks. For more information see Knowledge Base article Q176943.The Date Watch Wizard runs in the background while you are working in Excel. The Date Watch Wizard will suggest alternatives when you enter ambiguous text dates in cells or functions, change number formats to four-digit years when you type two-digit years, and display an alert when you open text files that contain two-digit years. For more information see Knowledge Base article Q176943.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other non-compliant 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.
Additional Testing Instructions Microsoft Excel has been designed for calculations in the year 2000. Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft 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 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:Caution! 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 Microsoft Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Microsoft 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 Microsoft 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).Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document. | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Portuguese (Brazil))
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| Office 97 Service Release 2 | ||||||||||||||||||||
| Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 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 Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Download the Office 97 SR2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates. VB/VBA uses the same serial date system, with the exception of 1-JAN-1900 through 28-FEB-1900, where the values are different by 1, as a result of a backward-compatibility issue for a bug in Lotus 1-2-3 that treats 1900 as a leap year. Previous versions of Excel recognize 01-JAN-1900 through 31-DEC-2078 as valid dates. 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, then even when the user types a YYYY date, it will by default display in a YY format. To avoid this, the default format can be changed to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 30 is 20XX, and equal to or greater than 30 is 19XX. So, for instance, "1/1/25" used to parse to 01-JAN-1925, but now parses to 01-JAN-2025. Suggest displaying dates in a YYYY format so the century is clearly shown. String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above. This may be a concern to some users because a formula such as =YEAR("1/1/25") returned 1925 in previous versions, but in Excel97 returns 2025. Note that this only happens when "1/1/25" is a string using a 2-digit year format. Also, the Date Migration Wizard, an Excel add-in, is available to aid the user in identifying and correcting these situations. See below for more information and a link to the Date Migration Wizard.
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: 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 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 KB articles Q180159 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. Using a format such as "Dec 98" or "12/98" will not function correctly in 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, Microsoft 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.)An undocumented behavior of Microsoft Query (all versions) may unintentionally encourage some users to enter a date criterion by specifying merely a month and day (such as "12/25"). In that instance, Query interprets the date as month and day of the current year. When the current year is equal to or greater than 2000, a malformed SQL statement is generated. In the event that this occurs, an error is generated and no data is returned. Avoiding this error is readily accomplished by entering a full and complete date. Microsoft recommends that all dates be entered in unambiguous formats, including a 4-digit year, but current versions of Microsoft Query also support windowing of 2-digit year dates as described in the Excel Year 2000 Product Guides. Due to the ambiguous nature of text dates, in general they will always have 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 Microsoft 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 not 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 or concern because users who use a date format with an order other than M-d-y will experience interpretive miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned concerns.
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel97: The Date Migration Wizard is designed to help users find instances where date-related arguments are referencing text dates that only specify the last two digits of a year. This can cause changes in calculation from previous versions of Microsoft Excel. For more information see Knowledge Base article Q176943.The Date Fix Wizard helps users find errors where the wrong century was entered for a date. It also allows the user to change date formats in a workbook to formats that display four digits of the year. Finally, it allows the user to scan workbooks for the earliest and latest dates in workbooks. For more information see Knowledge Base article Q176943.The Date Watch Wizard runs in the background while you are working in Excel. The Date Watch Wizard will suggest alternatives when you enter ambiguous text dates in cells or functions, change number formats to four-digit years when you type two-digit years, and display an alert when you open text files that contain two-digit years. For more information see Knowledge Base article Q176943.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other non-compliant 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.
Additional Testing Instructions Microsoft Excel has been designed for calculations in the year 2000. Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft 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 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:Caution! 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 Microsoft Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Microsoft 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 Microsoft 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).Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document. | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Portuguese)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| Office 97 Service Pack 2 | ||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 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 Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Download the Office 97 SR2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates. VB/VBA uses the same serial date system, with the exception of 1-JAN-1900 through 28-FEB-1900, where the values are different by 1, as a result of a backward-compatibility issue for a bug in Lotus 1-2-3 that treats 1900 as a leap year. Previous versions of Excel recognize 01-JAN-1900 through 31-DEC-2078 as valid dates. 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, then even when the user types a YYYY date, it will by default display in a YY format. To avoid this, the default format can be changed to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 30 is 20XX, and equal to or greater than 30 is 19XX. So, for instance, "1/1/25" used to parse to 01-JAN-1925, but now parses to 01-JAN-2025. Suggest displaying dates in a YYYY format so the century is clearly shown. String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above. This may be a concern to some users because a formula such as =YEAR("1/1/25") returned 1925 in previous versions, but in Excel97 returns 2025. Note that this only happens when "1/1/25" is a string using a 2-digit year format. Also, the Date Migration Wizard, an Excel add-in, is available to aid the user in identifying and correcting these situations. See below for more information and a link to the Date Migration Wizard.
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: 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 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 KB articles Q180159 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. Using a format such as "Dec 98" or "12/98" will not function correctly in 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, Microsoft 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.)An undocumented behavior of Microsoft Query (all versions) may unintentionally encourage some users to enter a date criterion by specifying merely a month and day (such as "12/25"). In that instance, Query interprets the date as month and day of the current year. When the current year is equal to or greater than 2000, a malformed SQL statement is generated. In the event that this occurs, an error is generated and no data is returned. Avoiding this error is readily accomplished by entering a full and complete date. Microsoft recommends that all dates be entered in unambiguous formats, including a 4-digit year, but current versions of Microsoft Query also support windowing of 2-digit year dates as described in the Excel Year 2000 Product Guides. Due to the ambiguous nature of text dates, in general they will always have 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 Microsoft 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 not 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 or concern because users who use a date format with an order other than M-d-y will experience interpretive miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned concerns.
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel97: The Date Migration Wizard is designed to help users find instances where date-related arguments are referencing text dates that only specify the last two digits of a year. This can cause changes in calculation from previous versions of Microsoft Excel. For more information see Knowledge Base article Q176943.The Date Fix Wizard helps users find errors where the wrong century was entered for a date. It also allows the user to change date formats in a workbook to formats that display four digits of the year. Finally, it allows the user to scan workbooks for the earliest and latest dates in workbooks. For more information see Knowledge Base article Q176943.The Date Watch Wizard runs in the background while you are working in Excel. The Date Watch Wizard will suggest alternatives when you enter ambiguous text dates in cells or functions, change number formats to four-digit years when you type two-digit years, and display an alert when you open text files that contain two-digit years. For more information see Knowledge Base article Q176943.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other non-compliant 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.
Additional Testing Instructions Microsoft Excel has been designed for calculations in the year 2000. Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft 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 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:Caution! 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 Microsoft Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Microsoft 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 Microsoft 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).Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document. | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Russian)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| Office 97 Service Release 2 | ||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 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 Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Download the Office 97 SR2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates. VB/VBA uses the same serial date system, with the exception of 1-JAN-1900 through 28-FEB-1900, where the values are different by 1, as a result of a backward-compatibility issue for a bug in Lotus 1-2-3 that treats 1900 as a leap year. Previous versions of Excel recognize 01-JAN-1900 through 31-DEC-2078 as valid dates. 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, then even when the user types a YYYY date, it will by default display in a YY format. To avoid this, the default format can be changed to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 30 is 20XX, and equal to or greater than 30 is 19XX. So, for instance, "1/1/25" used to parse to 01-JAN-1925, but now parses to 01-JAN-2025. Suggest displaying dates in a YYYY format so the century is clearly shown. String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above. This may be a concern to some users because a formula such as =YEAR("1/1/25") returned 1925 in previous versions, but in Excel97 returns 2025. Note that this only happens when "1/1/25" is a string using a 2-digit year format. Also, the Date Migration Wizard, an Excel add-in, is available to aid the user in identifying and correcting these situations. See below for more information and a link to the Date Migration Wizard.
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: 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 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 KB articles Q180159 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. Using a format such as "Dec 98" or "12/98" will not function correctly in 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, Microsoft 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.)An undocumented behavior of Microsoft Query (all versions) may unintentionally encourage some users to enter a date criterion by specifying merely a month and day (such as "12/25"). In that instance, Query interprets the date as month and day of the current year. When the current year is equal to or greater than 2000, a malformed SQL statement is generated. In the event that this occurs, an error is generated and no data is returned. Avoiding this error is readily accomplished by entering a full and complete date. Microsoft recommends that all dates be entered in unambiguous formats, including a 4-digit year, but current versions of Microsoft Query also support windowing of 2-digit year dates as described in the Excel Year 2000 Product Guides. Due to the ambiguous nature of text dates, in general they will always have 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 Microsoft 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 not 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 or concern because users who use a date format with an order other than M-d-y will experience interpretive miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned concerns.
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel97: The Date Migration Wizard is designed to help users find instances where date-related arguments are referencing text dates that only specify the last two digits of a year. This can cause changes in calculation from previous versions of Microsoft Excel. For more information see Knowledge Base article Q176943.The Date Fix Wizard helps users find errors where the wrong century was entered for a date. It also allows the user to change date formats in a workbook to formats that display four digits of the year. Finally, it allows the user to scan workbooks for the earliest and latest dates in workbooks. For more information see Knowledge Base article Q176943.The Date Watch Wizard runs in the background while you are working in Excel. The Date Watch Wizard will suggest alternatives when you enter ambiguous text dates in cells or functions, change number formats to four-digit years when you type two-digit years, and display an alert when you open text files that contain two-digit years. For more information see Knowledge Base article Q176943.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other non-compliant 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.
Additional Testing Instructions Microsoft Excel has been designed for calculations in the year 2000. Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft 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 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:Caution! 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 Microsoft Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Microsoft 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 Microsoft 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).Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document. | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Slovak)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| none | ||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 Nov 1999 | ||||||||||||||||||||
|
Description of how the product handles dates: Storage : Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates. VB/VBA uses the same serial date system, with the exception of 1-JAN-1900 through 28-FEB-1900, where the values are different by 1, as a result of a backward-compatibility issue for a bug in Lotus 1-2-3 that treats 1900 as a leap year. Previous versions of Excel recognize 01-JAN-1900 through 31-DEC-2078 as valid dates.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, then even when the user types a YYYY date, it will by default display in a YY format. To avoid this, the default format can be changed to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 30 is 20XX, and equal to or greater than 30 is 19XX. So, for instance, "1/1/25" used to parse to 01-JAN-1925, but now parses to 01-JAN-2025. Suggest displaying dates in a YYYY format so the century is clearly shown. String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above. This may be a concern to some users because a formula such as =YEAR("1/1/25") returned 1925 in previous versions, but in Excel97 returns 2025. Note that this only happens when "1/1/25" is a string using a 2-digit year format. Also, the Date Migration Wizard, an Excel add-in, is available to aid the user in identifying and correcting these situations. See below for more information and a link to the Date Migration Wizard.
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: 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 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 KB article Q180159 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. Using a format such as "Dec 98" or "12/98" will not function correctly in 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, Microsoft 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.)An undocumented behavior of Microsoft Query (all versions) may unintentionally encourage some users to enter a date criterion by specifying merely a month and day (such as "12/25"). In that instance, Query interprets the date as month and day of the current year. When the current year is equal to or greater than 2000, a malformed SQL statement is generated. In the event that this occurs, an error is generated and no data is returned. Avoiding this error is readily accomplished by entering a full and complete date. Microsoft recommends that all dates be entered in unambiguous formats, including a 4-digit year, but current versions of Microsoft Query also support windowing of 2-digit year dates as described in the Excel Year 2000 Product Guides. Due to the ambiguous nature of text dates, in general they will always have 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 Microsoft 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 not 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 or concern because users who use a date format with an order other than M-d-y will experience interpretive miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned concerns.
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel 97: THE DATE FIX WIZARD ADD-IN The Date Fix Wizard add-in for Microsoft Excel 97 allows you to manage dates more effectively by giving you the means to do the following:
THE DATE MIGRATION WIZARD ADD-IN The Date Migration Wizard add-in for Microsoft Excel 97 helps you ensure that dates with 2-digit years are handled correctly when you open a workbook that was created in an earlier version of Microsoft Excel. More specifically, the Date Migration Wizard searches workbooks for functions that contain 2-digit years that fall within the range 20 through 29 in text dates. (Excel 98 treats 2-digit years in this date range differently from earlier versions of Excel). THE DATE WATCH WIZARD ADD-IN The Date Watch Wizard is an add-in program for Microsoft Excel 97 that runs in the background while you work and does the following:
To download these add-ins for Excel 97 (German) go to: http://www.microsoft.com/germany/office/excel/enhancements/xly2000.htmTesting guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other non-compliant 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.
Additional Testing Instructions Microsoft Excel has been designed for calculations in the year 2000. Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft 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 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:Caution! 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 Microsoft Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Microsoft 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 Microsoft 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.)Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document. | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Slovenian)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| Office 97 Service Release 2 | ||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 Nov 1999 | ||||||||||||||||||||
|
Prerequisites: Download the Office 97 SR2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates. VB/VBA uses the same serial date system, with the exception of 1-JAN-1900 through 28-FEB-1900, where the values are different by 1, as a result of a backward-compatibility issue for a bug in Lotus 1-2-3 that treats 1900 as a leap year. Previous versions of Excel recognize 01-JAN-1900 through 31-DEC-2078 as valid dates. 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, then even when the user types a YYYY date, it will by default display in a YY format. To avoid this, the default format can be changed to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 30 is 20XX, and equal to or greater than 30 is 19XX. So, for instance, "1/1/25" used to parse to 01-JAN-1925, but now parses to 01-JAN-2025. Suggest displaying dates in a YYYY format so the century is clearly shown. String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above. This may be a concern to some users because a formula such as =YEAR("1/1/25") returned 1925 in previous versions, but in Excel97 returns 2025. Note that this only happens when "1/1/25" is a string using a 2-digit year format. Also, the Date Migration Wizard, an Excel add-in, is available to aid the user in identifying and correcting these situations. See below for more information and a link to the Date Migration Wizard.
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: 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 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 KB article Q180159 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. Using a format such as "Dec 98" will not function correctly in 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, Microsoft 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.)Due to the ambiguous nature of text dates, in general they will always have 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 Microsoft 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 not 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 or concern because users who use a date format with an order other than M-d-y will experience interpretive miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned concerns.
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel 97: THE DATE FIX WIZARD ADD-IN The Date Fix Wizard add-in for Microsoft Excel 97 allows you to manage dates more effectively by giving you the means to do the following:
THE DATE MIGRATION WIZARD ADD-IN The Date Migration Wizard add-in for Microsoft Excel 97 helps you ensure that dates with two-digit years are handled correctly when you open a workbook that was created in an earlier version of Microsoft Excel. More specifically, the Date Migration Wizard searches workbooks for functions that contain two-digit years that fall within the range 20 through 29 in text dates. (Excel 98 treats 2-digit years in this date range differently from earlier versions of Excel). THE DATE WATCH WIZARD ADD-IN The Date Watch Wizard is an add-in program for Microsoft Excel 97 that runs in the background while you work and does the following:
To download these add-ins for Excel 97 (German) go to: http://www.microsoft.com/germany/office/excel/enhancements/xly2000.htmTesting guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other non-compliant 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.
Additional Testing Instructions Microsoft Excel has been designed for calculations in the year 2000. Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft 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 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:Caution! 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 Microsoft Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Microsoft 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 Microsoft 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.)Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document. | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Spanish)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| Office 97 Service Release 2 | ||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 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 Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Download the Office 97 SR2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates. VB/VBA uses the same serial date system, with the exception of 1-JAN-1900 through 28-FEB-1900, where the values are different by 1, as a result of a backward-compatibility issue for a bug in Lotus 1-2-3 that treats 1900 as a leap year. Previous versions of Excel recognize 01-JAN-1900 through 31-DEC-2078 as valid dates. 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, then even when the user types a YYYY date, it will by default display in a YY format. To avoid this, the default format can be changed to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 30 is 20XX, and equal to or greater than 30 is 19XX. So, for instance, "1/1/25" used to parse to 01-JAN-1925, but now parses to 01-JAN-2025. Suggest displaying dates in a YYYY format so the century is clearly shown. String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above. This may be a concern to some users because a formula such as =YEAR("1/1/25") returned 1925 in previous versions, but in Excel97 returns 2025. Note that this only happens when "1/1/25" is a string using a 2-digit year format. Also, the Date Migration Wizard, an Excel add-in, is available to aid the user in identifying and correcting these situations. See below for more information and a link to the Date Migration Wizard.
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: 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 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 KB articles Q180159 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. Using a format such as "Dec 98" or "12/98" will not function correctly in 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, Microsoft 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.)An undocumented behavior of Microsoft Query (all versions) may unintentionally encourage some users to enter a date criterion by specifying merely a month and day (such as "12/25"). In that instance, Query interprets the date as month and day of the current year. When the current year is equal to or greater than 2000, a malformed SQL statement is generated. In the event that this occurs, an error is generated and no data is returned. Avoiding this error is readily accomplished by entering a full and complete date. Microsoft recommends that all dates be entered in unambiguous formats, including a 4-digit year, but current versions of Microsoft Query also support windowing of 2-digit year dates as described in the Excel Year 2000 Product Guides. Due to the ambiguous nature of text dates, in general they will always have 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 Microsoft 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 not 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 or concern because users who use a date format with an order other than M-d-y will experience interpretive miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned concerns.
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel97: The Date Migration Wizard is designed to help users find instances where date-related arguments are referencing text dates that only specify the last two digits of a year. This can cause changes in calculation from previous versions of Microsoft Excel. For more information see Knowledge Base article Q176943.The Date Fix Wizard helps users find errors where the wrong century was entered for a date. It also allows the user to change date formats in a workbook to formats that display four digits of the year. Finally, it allows the user to scan workbooks for the earliest and latest dates in workbooks. For more information see Knowledge Base article Q176943.The Date Watch Wizard runs in the background while you are working in Excel. The Date Watch Wizard will suggest alternatives when you enter ambiguous text dates in cells or functions, change number formats to four-digit years when you type two-digit years, and display an alert when you open text files that contain two-digit years. For more information see Knowledge Base article Q176943.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other non-compliant 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.
Additional Testing Instructions Microsoft Excel has been designed for calculations in the year 2000. Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft 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 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:Caution! 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 Microsoft Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Microsoft 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 Microsoft 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).Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document. | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Swedish)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| Office 97 Service Release 2 | ||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 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 Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Download the Office 97 SR2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates. VB/VBA uses the same serial date system, with the exception of 1-JAN-1900 through 28-FEB-1900, where the values are different by 1, as a result of a backward-compatibility issue for a bug in Lotus 1-2-3 that treats 1900 as a leap year. Previous versions of Excel recognize 01-JAN-1900 through 31-DEC-2078 as valid dates. 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, then even when the user types a YYYY date, it will by default display in a YY format. To avoid this, the default format can be changed to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 30 is 20XX, and equal to or greater than 30 is 19XX. So, for instance, "1/1/25" used to parse to 01-JAN-1925, but now parses to 01-JAN-2025. Suggest displaying dates in a YYYY format so the century is clearly shown. String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above. This may be a concern to some users because a formula such as =YEAR("1/1/25") returned 1925 in previous versions, but in Excel97 returns 2025. Note that this only happens when "1/1/25" is a string using a 2-digit year format. Also, the Date Migration Wizard, an Excel add-in, is available to aid the user in identifying and correcting these situations. See below for more information and a link to the Date Migration Wizard.
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: 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 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 KB articles Q180159 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. Using a format such as "Dec 98" or "12/98" will not function correctly in 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, Microsoft 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.)An undocumented behavior of Microsoft Query (all versions) may unintentionally encourage some users to enter a date criterion by specifying merely a month and day (such as "12/25"). In that instance, Query interprets the date as month and day of the current year. When the current year is equal to or greater than 2000, a malformed SQL statement is generated. In the event that this occurs, an error is generated and no data is returned. Avoiding this error is readily accomplished by entering a full and complete date. Microsoft recommends that all dates be entered in unambiguous formats, including a 4-digit year, but current versions of Microsoft Query also support windowing of 2-digit year dates as described in the Excel Year 2000 Product Guides. Due to the ambiguous nature of text dates, in general they will always have 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 Microsoft 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 not 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 or concern because users who use a date format with an order other than M-d-y will experience interpretive miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned concerns.
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel97: The Date Migration Wizard is designed to help users find instances where date-related arguments are referencing text dates that only specify the last two digits of a year. This can cause changes in calculation from previous versions of Microsoft Excel. For more information see Knowledge Base article Q176943.The Date Fix Wizard helps users find errors where the wrong century was entered for a date. It also allows the user to change date formats in a workbook to formats that display four digits of the year. Finally, it allows the user to scan workbooks for the earliest and latest dates in workbooks. For more information see Knowledge Base article Q176943.The Date Watch Wizard runs in the background while you are working in Excel. The Date Watch Wizard will suggest alternatives when you enter ambiguous text dates in cells or functions, change number formats to four-digit years when you type two-digit years, and display an alert when you open text files that contain two-digit years. For more information see Knowledge Base article Q176943.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other non-compliant 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.
Additional Testing Instructions Microsoft Excel has been designed for calculations in the year 2000. Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft 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 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:Caution! 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 Microsoft Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Microsoft 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 Microsoft 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).Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document. | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Thai)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| MSQuery software update | ||||||||||||||||||||
| Microsoft Thai Windows 95, Thai Windows 98, Thai Windows NT4 (no specific Service Pack is required, though SP4 is recommended) | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 Nov 1999 | ||||||||||||||||||||
|
Prerequisite for Year 2000 Compliance—MSQuery Patch: To resolve known issues with Excel 97 Thai, Microsoft Query must be updated (see Knowledge Base article Q187698 – MS Query uses 1900 date when two digits are used for year in a query). This issue is addressed for the English version of Excel 97 in Service Release 2. Since this Service Release is not presently available for the Thai version, it is recommended that the software update be applied to address the issue in the Thai version of Excel 97. The software update can be downloaded and installed from the following location: http://www.microsoft.com/thailand/download/xl97y2k.exeSpecial Note for Thai versions of Excel: How the product handles dates:
Planning for 4-digit-year display is important in programs such as Excel, where columns may be fixed by the worksheet author with widths that are too narrow for 4-digit years.
Two-digit shortcut handling: See the preceding discussion. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. For more information, see Knowledge Base (KB) article Q164406.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:
For more information about these add-in tools, see KB article Q176943.Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with other 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 whether dates are being properly used. The following table can be used to guide testing of Excel within your organization.
Additional Testing Instructions Excel has been designed for calculations in the year 2000 and beyond. 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").
Caution! 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 1 minute, 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 2000 as 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 4, 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. For more information, see KB article Q181370. Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Turkish)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| Office 97 Service Release 2 | ||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 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 Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Download the Office 97 SR2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates. VB/VBA uses the same serial date system, with the exception of 1-JAN-1900 through 28-FEB-1900, where the values are different by 1, as a result of a backward-compatibility issue for a bug in Lotus 1-2-3 that treats 1900 as a leap year. Previous versions of Excel recognize 01-JAN-1900 through 31-DEC-2078 as valid dates. 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, then even when the user types a YYYY date, it will by default display in a YY format. To avoid this, the default format can be changed to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 30 is 20XX, and equal to or greater than 30 is 19XX. So, for instance, "1/1/25" used to parse to 01-JAN-1925, but now parses to 01-JAN-2025. Suggest displaying dates in a YYYY format so the century is clearly shown. String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above. This may be a concern to some users because a formula such as =YEAR("1/1/25") returned 1925 in previous versions, but in Excel97 returns 2025. Note that this only happens when "1/1/25" is a string using a 2-digit year format. Also, the Date Migration Wizard, an Excel add-in, is available to aid the user in identifying and correcting these situations. See below for more information and a link to the Date Migration Wizard.
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: 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 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 KB articles Q180159 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. Using a format such as "Dec 98" or "12/98" will not function correctly in 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, Microsoft 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.)An undocumented behavior of Microsoft Query (all versions) may unintentionally encourage some users to enter a date criterion by specifying merely a month and day (such as "12/25"). In that instance, Query interprets the date as month and day of the current year. When the current year is equal to or greater than 2000, a malformed SQL statement is generated. In the event that this occurs, an error is generated and no data is returned. Avoiding this error is readily accomplished by entering a full and complete date. Microsoft recommends that all dates be entered in unambiguous formats, including a 4-digit year, but current versions of Microsoft Query also support windowing of 2-digit year dates as described in the Excel Year 2000 Product Guides. Due to the ambiguous nature of text dates, in general they will always have 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 Microsoft 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 not 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 or concern because users who use a date format with an order other than M-d-y will experience interpretive miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned concerns.
Microsoft has created three add-in tools to help users identify Year 2000 issues in solutions created with Microsoft Excel97: The Date Migration Wizard is designed to help users find instances where date-related arguments are referencing text dates that only specify the last two digits of a year. This can cause changes in calculation from previous versions of Microsoft Excel. For more information see Knowledge Base article Q176943.The Date Fix Wizard helps users find errors where the wrong century was entered for a date. It also allows the user to change date formats in a workbook to formats that display four digits of the year. Finally, it allows the user to scan workbooks for the earliest and latest dates in workbooks. For more information see Knowledge Base article Q176943.The Date Watch Wizard runs in the background while you are working in Excel. The Date Watch Wizard will suggest alternatives when you enter ambiguous text dates in cells or functions, change number formats to four-digit years when you type two-digit years, and display an alert when you open text files that contain two-digit years. For more information see Knowledge Base article Q176943.
Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other non-compliant 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.
Additional Testing Instructions Microsoft Excel has been designed for calculations in the year 2000. Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft 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 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:Caution! 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 Microsoft Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Microsoft 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 Microsoft 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).Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document. | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Excel 97 8.0 (Vietnamese)
| 01 Jan 1900 - 31 Dec 9999 | ||||||||||||||||||||
| MSQuery software update | ||||||||||||||||||||
| Microsoft Vietnamese Windows 95 | ||||||||||||||||||||
| System clock | ||||||||||||||||||||
| 15 Nov 1999 | ||||||||||||||||||||
|
Prerequisite for Year 2000 Compliance—MSQuery Patch: To resolve all known issues with Excel 97 Vietnamese, Microsoft Query must be updated (see Knowledge Base Article Q187698 – MS Query uses 1900 date when two digits are used for year in a query). This issue is addressed for the English version of Excel 97 in Service Release 2. Since this Service Release is not presently available for the Vietnamese version, a software update must be applied to resolve the issue. For information on obtaining and installing the necessary files for this software update, contact the Microsoft subsidiary in Vietnam:Telephone: 84-4-8251955 Fax: 84-4-8261222 How the product handles dates:
Planning for 4-digit-year display is important in programs such as Excel, where columns may be fixed by the worksheet author with widths that are too narrow for 4-digit years.
Two-digit shortcut handling: See the preceding discussion. Conversion of 2-digit shortcut dates assumes a date window of 1930 through 2029. For more information, see Knowledge Base (KB) article Q164406. 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:
For more information about these add-in tools, see KB article Q176943.Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because side effects with other 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 whether dates are being properly used. The following table can be used to guide testing of Excel within your organization.
Additional Testing Instructions Excel has been designed for calculations in the year 2000 and beyond. 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").
Caution! 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 1 minute, 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 2000 as 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 4, 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. For more information, see KB article Q181370. Excel 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Excel 97, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.
| ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Chinese - Simplified)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Chinese - Traditional)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Czech)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Danish)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Dutch)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (English)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Finnish)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (French)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (German)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Greek)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Hungarian)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Italian)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Japanese)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Korean)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Norwegian)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Polish)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Portuguese (Brazil))
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Portuguese)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Russian)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Spanish)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Swedish)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 4.x (Turkish)
| 01 Jan 1970 - 31 Jan 2079 | ||
| Install Exchange Client (16-bit) version 4.0 Service Pack 4. See below for download. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
Prerequisites: Install Exchange Client (16-bit) version 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes (choose appropriate language)For end-to-end compliance, use a Year 2000 compliant server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 5.XX (Chinese - Simplified)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Exchange Client (16-bit) version 5.0 does not require a service pack for Year 2000 compliance.If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 5.XX (Chinese - Traditional)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Exchange Client (16-bit) version 5.0 does not require a service pack for Year 2000 compliance.If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 5.XX (English)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Exchange Client (16-bit) version 5.0 does not require a service pack for Year 2000 compliance.If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 5.XX (French)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Exchange Client (16-bit) version 5.0 does not require a service pack for Year 2000 compliance.If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 5.XX (German)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Exchange Client (16-bit) version 5.0 does not require a service pack for Year 2000 compliance.If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 5.XX (Japanese)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Exchange Client (16-bit) version 5.0 does not require a service pack for Year 2000 compliance.If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 5.XX (Korean)
| 01 Jan 1970 - 31 Jan 2079 | ||
| See below | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
Prerequisites: Exchange Client (16-bit) version 5.0 does not require a service pack for Year 2000 compliance.If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (16-bit) 5.XX (Portuguese (Brazil))
| 01 Jan 1970 - 31 Jan 2079 | ||
| Exchange Client (16-bit) version 5.0 does not require a service pack for Year 2000 compliance. | ||
| Windows 3.11 | ||
| Operating System Clock | ||
| 25 May 1999 | ||
|
If Schedule+ is used, please see the Schedule+ product guide for details on compliance information. How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the Exchange Client are parsed into years 1980 through 2079. Two-digit displays use the short date format specified in the International applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, use a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well, for example client transports, server connectors, gateways. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on Microsoft Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter normally. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (Mac) 4.XX (English)
| 01 Jan 1980 - 31 Dec 2035 | ||
| Exchange Server 4.0 Service Pack 5, Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. Exchange Client for Macintosh 4.0 Service Pack 4. | ||
| Apple System 7.1 or higher, Macintosh operating system 7.6.1 or higher | ||
| Operating System Clock | ||
| 04 Dec 1998 | ||
|
How the product handles dates:
Formatting. Dates are displayed in 2-digit and 4-digit year formats, using the short date format (YY) and long date format (YYYY) specified in the Date & Time applet in the Control Panel. The date entry fields in the Find/Filter Items dialog accept only inputs in the 2-digit year format.
Two-digit shortcut handling: Two-digit year entries in the range of 80 – 99, 00 – 35 in the Exchange Client are parsed into years 1980 through 2035. Two-digit displays use the short date format specified in the Date & Time applet in the Control Panel. Recommendations for compliance: Install Exchange Client for Macintosh 4.0 Service Pack 4 ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg4.0/Sp4Common date usage error: For end-to-end compliance when using the Exchange Client, the user needs a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5, Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example, client transports, server connectors, gateways. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (Mac) 5.XX (English)
| 01 Jan 1980 - 31 Dec 2035 | ||
| Exchange Server 4.0 Service Pack 5, Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. | ||
| Apple System 7.1 or higher, Macintosh operating system 7.6.1 or higher | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the range of 80 – 99, 00 – 35 in the Exchange Client are parsed into years 1980 through 2035. Two-digit displays use the short date format specified in the Date & Time applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, users need a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example, client transports, server connectors, gateways.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (Mac) 5.XX (French)
| 01 Jan 1980 - 31 Dec 2035 | ||
| Exchange Server 4.0 Service Pack 5, Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. | ||
| Apple System 7.1 or higher, Macintosh operating system 7.6.1 or higher | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the range of 80 – 99, 00 – 35 in the Exchange Client are parsed into years 1980 through 2035. Two-digit displays use the short date format specified in the Date & Time applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, users need a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example, client transports, server connectors, gateways.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (Mac) 5.XX (German)
| 01 Jan 1980 - 31 Dec 2035 | ||
| Exchange Server 4.0 Service Pack 5, Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. | ||
| Apple System 7.1 or higher, Macintosh operating system 7.6.1 or higher | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the range of 80 – 99, 00 – 35 in the Exchange Client are parsed into years 1980 through 2035. Two-digit displays use the short date format specified in the Date & Time applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, users need a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example, client transports, server connectors, gateways.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client (Mac) 5.XX (Japanese)
| 01 Jan 1980 - 31 Dec 2035 | ||
| Exchange Server 4.0 Service Pack 5, Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. | ||
| Apple System 7.1 or higher, Macintosh operating system 7.6.1 or higher | ||
| Operating System Clock | ||
| 03 Dec 1998 | ||
|
How the product handles dates:
Two-digit shortcut handling: Two-digit year entries in the range of 80 – 99, 00 – 35 in the Exchange Client are parsed into years 1980 through 2035. Two-digit displays use the short date format specified in the Date & Time applet in the Control Panel.
Common date usage error: For end-to-end compliance when using the Exchange Client, users need a Year 2000 compliant mail server, including Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 1 or greater. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example, client transports, server connectors, gateways.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 4.XX (Arabic)
| 01 Jan 1970 - 05 Feb 2036 | |||
| See below | |||
| Windows 95, or Windows NT 4 .0 | |||
| System Clock | |||
| 15 Dec 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Chinese - Simplified)
| 01 Jan 1970 - 05 Feb 2036 | |||
| See below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 09 Dec 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Chinese - Traditional)
| 01 Jan 1970 - 05 Feb 2036 | |||
| See below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 09 Dec 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Czech)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Danish)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Dutch)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (English)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Finnish)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (French)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (German)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Greek)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Hebrew)
| 01 Jan 1970 - 05 Feb 2036 | |||
| See below | |||
| Windows 95, or Windows NT 4 .0 | |||
| System Clock | |||
| 15 Dec 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Hungarian)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Italian)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Japanese)
| 01 Jan 1970 - 05 Feb 2036 | |||
| See below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 09 Dec 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Korean)
| 01 Jan 1970 - 05 Feb 2036 | |||
| See below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 09 Dec 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Norwegian)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Polish)
| 01 Jan 1970 - 05 Feb 2036 | |||
| See below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 09 Dec 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Portuguese (Brazil))
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 04 Dec 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Portuguese)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Russian)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Spanish)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Swedish)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 4.XX (Turkish)
| 01 Jan 1970 - 05 Feb 2036 | |||
| see below | |||
| Windows 95, Windows NT 3.51 with SP4 or greater, or Windows NT 4 .0 | |||
| System Clock | |||
| 30 Nov 1998 | |||
|
Prerequisites - If you use Schedule+, please see the Schedule+ product guide for details on compliance 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
Exchange Client 5.XX (Chinese - Simplified)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Chinese - Traditional)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Czech)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Danish)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Dutch)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (English)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 15 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Finnish)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (French)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (German)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Greek)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Hungarian)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Italian)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Japanese)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Korean)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Norwegian)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Polish)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Portuguese (Brazil))
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Portuguese)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Russian)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Spanish)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Client 5.XX (Swedish)
| 01 Jan 1970 - 05 Feb 2036 | ||
| If you use Schedule+, please see the Schedule+ product guide for details on compliance information. | ||
| Windows 95, Windows NT 3.51 with SP5 or greater, or Windows NT 4 .0 | ||
| System Clock | ||
| 18 Jan 1999 | ||
|
Description of how the product handles dates:
2-digit shortcut handling: All 2-digit year entries in the Exchange Client are parsed into years 1980 through 2079. All 2-digit displays use the short date format specified in the Regional Settings applet in the Control Panel. Common date usage error: For full compliance, use a Year 2000 compliant mail server that has been tested with the Exchange Client. Note that other parts of e-mail connectivity need to be Year 2000 compliant as well for full compliance, for example client transports, server connectors, gateways, etc. The Microsoft Exchange Forms Designer is a Visual Basic 4.0 16-bit application. It will default 2-digit dates to the century of the current system date. The Short and Long date fields on custom EFD forms are stored as string values. These custom date fields will not sort or filter correctly. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with Year 2000 compliant Exchange Server and other Microsoft products can be conducted safely. See Exchange Server compliance information for details on server issues. | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Chinese - Simplified)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language 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
Exchange Server - Enterprise 4.0 (Chinese - Traditional)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language 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
Exchange Server - Enterprise 4.0 (Czech)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language 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
Exchange Server - Enterprise 4.0 (Danish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language 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
Exchange Server - Enterprise 4.0 (Dutch)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language 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
Exchange Server - Enterprise 4.0 (English)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 4.0 Service Pack 5 (SP 5) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) or Windows NT 3.51 Service Pack 5 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This included Windows NT Server 4.0 SP3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and discusses the way these components function together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. All components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange 4.0 is year 2000 compliant when used with Service Pack 5 (SP5). How can the customer make the product compliant? Exchange 4.0 SP5 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg4.0/SP5This is the location of the English version. French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/When the service pack 5 is installed, Exchange Server 4.0 is year 2000 compliant. Description of Date Handling: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database : The Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store (MDB): Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2 digit year in those cases where other components hands the MDB an internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range to of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, the Exchange Information Store will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange Information Store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2-digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Active Messaging and MAPI: Active Messaging and MAPI uses a 64-bit FILETIME. Any Active Messaging or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4-byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2036.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to internet and X.400 standards that only support 2 digits the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant. All levels of encryption were tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The IMS stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2 digits representing the year. See Microsoft Exchange Information Store for more information. When the IMS is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however, due to internet standards that only support 2 digits, the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMI in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange MIGRATION All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2-digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2-digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4 digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any 2-digit dates received from and/or expected by those Non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the Non Microsoft environment, however Microsoft can not assure our customers of the compliance of the Non Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, GroupWare, etc… applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (Finnish)
| - | ||
| 21 Sep 1999 | ||
|
The Microsoft Exchange Server package is made up of two parts, the client and the server. The client is either Microsoft Outlook or the Microsoft Exchange Client. The Microsoft Exchange Server is available in the following languages: English French German Japanese Microsoft Exchange Server packages other than the above languages contain the English version of the Microsoft Exchange Server and a localized language version of either Microsoft Outlook or Microsoft Exchange Client. To get year 2000 information about the Microsoft Exchange Server, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Server - Enterprise or Standard version and view the English documents.To get year 2000 information about Microsoft Outlook, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view Outlook version and language information.To get year 2000 information about the Microsoft Exchange client, go to the year 2000 product guide at: http://www.microsoft.com/technet/year2k/product/product.htm and view the Exchange Client version and language 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
Exchange Server - Enterprise 4.0 (French)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 4.0 Service Pack 5 (SP 5) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) or Windows NT 3.51 Service Pack 5 (see Note 2) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This included Windows NT Server 4.0 SP3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and discusses the way these components function together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. All components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange 4.0 is year 2000 compliant when used with Service Pack 5 (SP5). How can the customer make the product compliant? Exchange 4.0 SP5 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg4.0/SP5This is the location of the English version. French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/When the service pack 5 is installed, Exchange Server 4.0 is year 2000 compliant. Description of Date Handling: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database : The Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store (MDB): Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2 digit year in those cases where other components hands the MDB an internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range to of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, the Exchange Information Store will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange Information Store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2-digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Active Messaging and MAPI: Active Messaging and MAPI uses a 64-bit FILETIME. Any Active Messaging or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4-byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2036.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to internet and X.400 standards that only support 2 digits the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant. All levels of encryption were tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The IMS stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2 digits representing the year. See Microsoft Exchange Information Store for more information. When the IMS is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however, due to internet standards that only support 2 digits, the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMI in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange MIGRATION All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2-digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2-digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4 digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any 2-digit dates received from and/or expected by those Non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the Non Microsoft environment, however Microsoft can not assure our customers of the compliance of the Non Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, GroupWare, etc… applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Exchange Server - Enterprise 4.0 (German)
| 01 Jan 1970 - 19 Jan 2038 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Exchange 4.0 Service Pack 5 (SP 5) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT 4.0 Service Pack 4 (see Note 1) or Windows 3.51 Service Pack 5 (see Note 1) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows NT System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note 1: Please see the details on http://www.microsoft.com/technet/year2k/product/product.htm for the latest information on Windows NT Server. Exchange is Compliant when used with the Compliant or Compliant# version of Windows NT Server. This included Windows NT Server 4.0 SP3 with the latest hot fixes.The Microsoft Exchange Server will operate in the minimum range of Jan 1, 1970 - January 19, 2038. In many cases the Microsoft Exchange Server will operate in ranges that extend far beyond their parameters and stretch the range from 1601 through 60055. This document covers all of the Microsoft Exchange components and discusses the way these components function together and use dates. The document covers all products that are included in the Microsoft Exchange Server Enterprise edition, or that can be purchased separately. In addition, it covers the individual components that can be added to the Exchange Server Standard edition. All components combined together are referred to as Exchange. There are individual components that may be called out specifically, in order to give more details on how they use dates or how some features should be tested. Year 2000 information for the Exchange clients and Outlook are covered in their corresponding documents. What are the prerequisites? Exchange 4.0 is year 2000 compliant when used with Service Pack 5 (SP5). How can the customer make the product compliant? Exchange 4.0 SP5 is located on: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg4.0/SP5This is the location of the English version. French (FRN), German (GER) and Japanese (JPN) are located in the corresponding directories at ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/When the service pack 5 is installed, Exchange Server 4.0 is year 2000 compliant. Description of Date Handling: Listed below are the major components of Exchange and how each handle dates. Microsoft Exchange Server Database : The Extensible Storage Engine and the Exchange Server Database Engine are year 2000 compliant. The internal date range in years from 1900 to 2156. Jet uses the JET_LOGTIME structure. Date/Time structures the Exchange Server Database Engine uses: JET_LOGTIME structure (8 char's (bytes) representing date-time) Year is encoded as: char bYear; Date range for this structure is: 1900 - 2156
Microsoft Exchange Information Store (MDB): Internally the information store stores all year dates in 4 digits using the types FILETIME or SYSTIME. There are a few cases in which the information store accepts a 2 digit year in those cases where other components hands the MDB an internet standard RFC 822 message. In this case the information store stores these dates as the number of seconds since Jan 1st, 1986. This gives the information store a range to of 1986 – 2085. In the cases where dates are passed to the information store as a UTC_TIME string, the Exchange Information Store will convert the two digits using 1951 as the cut off for the range. If the year is in the range 51-99 the date is converted to be 1951-1999. If the year is in the range 00-50, the date is converted to 2000-2050. Date/Time structures the Exchange Information Store uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however due to internet standards that only support 2-digits, the MDB has to do the correct year 2000 conversion and supports a range of 1986 – 2050.
Active Messaging and MAPI: Active Messaging and MAPI uses a 64-bit FILETIME. Any Active Messaging or MAPI applications written that pass in a year 2000 compliant date will be stored correctly within Exchange. The internal date range in years from 1601 to 60055. Date/Time structures MAPI uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange Message Transfer Agent (MTA): The Exchange MTA is a X.400 standard MTA. X.400 itself is not year 2000 compliant. The ASN.1 type UTCTime defined by ISO/CCITT uses a 2-digit date format for years. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When these ASN.1 dates come in from other systems MTA converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the MTA uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digit dates the MTA has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Directory (DSA): The Exchange directory service uses X.500 industry standards which store dates in UTC time formats. UTC time format uses 2 digits to represent the year of each date. An example of a UTC time format is 980128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. Internally these dates are stored as a 4-byte int counting the number of seconds since January 1st, 1970. Thus the date range of DSA is January 1st, 1970 through January 19th, 2038. When these dates come in from other systems or components the directory converts them from the UTC format to determine the century. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures MAPI uses: UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ Date range for this structure is: 00 – 99, however due to X.500 standards that only support 2 digits the DSA has to do the correct year 2000 conversion and supports a range of 1970 – 2036.
Microsoft Exchange Administrator: The Exchange Administrator program has to be able to administer X.400 and X.500 components. To do so it has to be able to support ASN.1 and UTC time standards. Both of these standards store the year date values in two digits. An example of an ASN.1 and UTC time format is 970128131030Z which stands for 1/28/1998, 1:10:30pm, zulu (GMT) time. When the Administrator program uses these dates it converts them into 4 digits when needed. If the year is in the range 50-99 the date is converted to be 1950-1999. If the year is in the range 00-49, the date is converted to 2000-2049. Date/Time structures the Administrator program uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to internet and X.400 standards that only support 2 digits the Administrator program has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Exchange Key Management Server (KMS): The KMS server explicitly uses 4 digits to represent years for all storage of dates. The UTC_TIME string is used, but only for keeping track of when a cert is issued. Since the certs are internally tracked by minutes and hours the year digits as part of the date are not used, there for there are no issues making KMS year 2000 compliant. All levels of encryption were tested to verify year 2000 compliance. This includes testing with languages that support different levels of encryption.
Microsoft Exchange Internet Mail Service (IMS): The IMS stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the information store. RFC 822 messages store date formats with 2 digits representing the year. See Microsoft Exchange Information Store for more information. When the IMS is setup as a connector it reads information from the GWART. See MTA for more information. Date/Time structures the IMC uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055, however, due to internet standards that only support 2 digits, the IMS has to do the correct year 2000 conversion and supports a range of 1970 – 2038.
Microsoft Mail Connector Interchange (MSMI): All dates going to Exchange via MSMI in the P1 Envelope of a message are mapped to XOM objects of syntax OM_S_UTC_TIME_STRING which is a string presentation of the ASN.1 UTC time syntax used by the MTA. UTC time is a 2-digit year so the century is dropped going to Exchange and the MTA interprets the date into a 4-digit year. See the MTA for details. Dates from Exchange in the P1 envelope are ignored and dropped. Date/Time structures MSMI uses: ASN.1 string is any of the following: This is the format used for X.400 standards. /* UTC FORMAT TIME : YYMMDDHHmmZ */ /* OR YYMMDDHHmmssZ */ /* OR YYMMDDHHmmXhhmm WHERE X IS "-" OR "+" */ /* OR YYMMDDHHmmssXhhmm WHERE X IS "-" OR "+" */ UTC_TIME string (two digit year) 980128131030Z stands for 1/28/1998, 1:10:30pm, zulu (GMT) time Date range for this structure is: 00 – 99, however due to X.400 standards that only support 2 digits MSMI has to do the correct year 2000 conversion and supports a range of 1970 – 2038. Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 - 60055
Microsoft Exchange MIGRATION All dates going into Exchange in the content of a message are mapped to MAPI PT_ SYSTIME properties of MAPI type PT_SYSTIME. PT_SYSTIME encodes the year unambiguously, see MAPI for more information. Most other mail systems use 2-digit year format. Migration converts this from the 2-digit year format using different rules for each mail system. Below are the rules for each system: System: Rule: cc:Mail DB6: Add 1900 to the year that is passed from cc:Mail. Example: 110 is passed in for the year 2010. MSMail: The year is passed in as 4 digits from MSMail. Example 2010 is passed directly to Migration. Date/Time structures Migrations uses: Filetime structure (two DWORDs representing # of 100ns intervals since 1/1/1601)
Date range for this structure is: 1601 – 60055. Does the product support 2-digit shortcuts for date representation? Yes What is the logic for converting 2-digit shortcuts to 4 digits for the storage and calculation? There are some components within Exchange that use UTC, ASN.1, X.400 and X.500 standards which require dates to be stored in 2 digits. For these case any date that is the values 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. Are there some common pitfalls for use or testing of this product that may have caused the customer to use the product in a non-compliant fashion? Microsoft continues to promote the utilization of Internet standards within the Microsoft Exchange Server and continues to provide connectivity other vendors messaging systems. In doing so Microsoft has had to adapt Microsoft Exchange Server to convert any 2-digit dates received from and/or expected by those Non Microsoft systems. Microsoft has confirmed and tested the handling of dates within the Microsoft environment and in the passing to the Non Microsoft environment, however Microsoft can not assure our customers of the compliance of the Non Microsoft receiving environment. What are the recommended processes for customers to follow to better test the product in their environment? Setup a test environment that simulates part of their Exchange topology. When this is setup, change the system time on all servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Exchange environment. These are any workflow, GroupWare, etc… applications that the company uses to run their business. Microsoft would recommend that the customer roll forward the date to several various dates in the range 12/31/1999-12/31/2009 and test many different scenarios. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
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.  | ||