Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Office Standard 95 7.0 (Spanish)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System Clock | ||
| 12 Aug 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Office 95 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent Note: The below information refers to the code that is shared between Office 95 documents. Please see the individual applications for more detailed information on the product. Prerequisites An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmDescription of how the product handles dates: All dates and times that are displayed or query-able by the user are obtained from the operating system's date and time, stored as fully qualified four-digit year dates and displayed according to user settings in the operating system. Setup has no date sensitivity except in setup file removal. See below for testing implications For VBA and the shared Office object model: All dates and times displayed are obtained from the operating system clock. All dates are stored using a 4-digit year format. A date may be displayed in a 2-digit format (by formatting cells in an Excel worksheet for example) but the value is always stored as a 4-digit year value. Since a common programming language (VBA v4) is used by all applications, date handling for all applications can be tested by testing the VBA intrinsic commands. These intrinsic functions for date handling include: Now () CDate() CVDate() DateValue() Date() Date$() Format() DateAdd() DateDiff() DatePart() IsDate() Day() Month() Weekday() Year() Shared Object Model Methods and Properties Files stored in Office format (.xls, .doc, .ppt etc.) have date properties associated with them. These properties can be manipulated using VBA methods. Objects, Methods, Properties, and Collections possibly affected by Year 2000 Microsoft Office Language Reference Document Properties Object- Property type can be date e.g. msoPropertyTypeDate CreationDate Property LastPrintDate Property LastSaveTime Property PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth Add Method Condition Property FileSearch Object LastModified Property 2-digit shortcut handling: Advanced Find under File/Open allows the entry of 2-digit dates. Beyond Advance Find File, Office shared features support short dates as system display options only. See individual applications for additional information. In Advanced Find, distant future dates have little meaning relative to file creation dates. Therefore, the date is assumed to fall within a range between current year minus 90 years and plus 10 years. For example, in the year 1998 the date range spans from 1908 to 2008. See individual applications for additional shortcut logic. Logic is designed to be appropriate for particular application. The Office Document Properties dialog stores and displays file date information consistent with the 4-digit year format set in the Windows Control Panel Regional Settings. However, the date formatting used in the Custom Document Properties dialog, does not properly recognize two digit years past 1999, so organizations using dates in custom properties should include all four digits of the year when entering them. For VBA and the shared Office object model: In the original configuration, all 2 digit dates were assumed to belong to the current century as defined by the system clock. The logic rules that determine this are included in the oleaut32.dll shared resource file. In any particular computer configuration, this shared resource file may have been updated. This will occur if a browser (Internet Explorer 3.x or greater), Operating System (Windows 95 OEM Service Release 2.5, Windows 98, Windows NT 4, or other Office application is installed or updated using a newer oleaut32.dll file. In this case, the Office95 applications will use 2 digit date handling logic consistent with the oleaut32.dll version. Users should load oleaut32.dll v2.20.4122 or later to the c:\Windows\System (Windows 95) or c:\WINNT\System32 (Windows NT) directories for all affected computers. This will ensure that the date handling characteristics for 2 digit dates are consistent with the date window approach outlined above for all computers. For additional Information please see the VBA Year 2000 Product GuideRecommendations to meet compliance: 1) An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htm-2) See the Year 2000 Product Guide for your computer operating system and install prerequisite updates for Year 2000 compliance. Also see the Product Guide documents for individual Office 95 applications. 3) Set display of short dates to include four digit years, both in your control panel regional settings and in the default display formatting for each application. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data. If it is necessary to use plain text data, it should be saved and manipulated with the full four-digit year. Text values that contain date data should be checked to ensure that they contain the full four-digit year. Data entered or imported into Microsoft Office applications such as Microsoft Word or Microsoft PowerPoint, which do not have data typing in the document format, will be treated as simple text. Those applications should not be used to store dates for which calculations are based (except in the instance of document properties). Standard document properties can be consistently queried and used across all Microsoft Office applications for date queries and calculations, both programmatically and through the user interface, but user-defined custom properties could generate inconsistencies. For VBA and the shared Office object model: User-defined functions are a prime area of date handling errors. A poorly written function may lead to problems. Dates that are stored as strings can also be a problem if there is an error in the information. The VBA language will interpret a string as a date if by rearranging the month/day/year order a valid date can be found. For example, both 3/30/98 (March 30, 1998) and 187/3/1 (March 1, 187) are valid dates even though the month/day/year order have changed. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing across all Microsoft Office products can be conducted safely. Setup maintenance mode (for file removal), the only date sensitive portion of Microsoft Office setup, removes all templates except those installed in recent months. This does not affect Year 2000 compliance, but it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be otherwise. Area SubArea Microsoft’s Testing Summary File Open/Save Dialog Document Properties Document management features include file open/save bringing up the proper "OK to Replace?" confirmation dialog when attempting to save a file after the date/time has been changed; display of dates in results pane of dialog; sorting of dates in results pane of file open/save dialog. Findfast Creation date of index Create an index with the date set to the year 2000. Click Index, create index, select the index mentioned and hit Information. Ensure that the date shown says the year 2000 or 00 depending on the regional settings. Last modified date of index Have Findfast set to update itself every 3 minutes. Set the system date to December 31, 1999, and have it roll over to the year 2000. Verify that updating mechanism for Findfast is not affected. Creation date of file Create a file created on January 1, 2000. Perform a search using an Office App for files created after December 30, 1999, and verify that the file was found. Findfast (cont.) Last modified date of file Create a file last modified on January 1, 2000. Perform a search using an Office App for files last modified after December 30, 1999 and verify that the file was found. Last printed date of file Create a file last modified on January 1, 2000. Perform a search using an Office App for files last modified after December 30, 1999 and verify that the file was found. Custom date property Create a file with a custom date property of January 1, 2000. Perform a search using an Office App for files with that property set to a date later than December 30, 1999 and verify that the file was found. Leap year testing Repeat the above 5 tests using February 29 and 28, 2000, 2001, and 2004, as the dates used. Log file Verify that the log file shows the year 00 for any logs in the year 2000 if the regional settings are set to 2 digit format, and 2000 if the regional settings are set to 4 digit format. Displayed dates Verify that the displayed dates for the creation/last modified dates of the index show 00 for the year 2000 if the regional settings are set to 2 digit format, and 2000 if the regional settings are set to 4 digit format. Setup Complete Install Complete install is a superset of other options. Should be performed on clean machine and on machine with Office version 95 installed with all combinations spanning the turn of the century. Maintenance Mode Remove All For VBA and the shared Office object model: Users testing applications written in VBA should be especially careful to test four main problem areas: User-defined functions: Many applications contain user-defined functions written in VBA to deal with dates in various ways. Many of these functions store date values as strings. Manipulating these values improperly can result in date handling errors that are outside of the scope of the testing that was done at Microsoft. The date usage error described above can cause problems if an error handling routine is meant to catch improperly entered dates. Since VBA rarely generates an error when a string date is used as an input, an error handling routine is unlikely to be called. In this case the proper programming technique would be to validate the data using code instead of relying on an error to signal an improper date. Interactions between computers with varying versions of oleaut32.dll should be tested to ensure that the two digit assumptions built into this system file do not cause problems. Code Example: The following example illustrates the date window in action with various input dates. Depending on the version of the file oleaut32.dll installed, this code will produce varying results. Sub TestDate() Dim MyDate As Date MyDate = "1/1/00" Format MyDate, "mm/dd/yyyy" MsgBox MyDate End Sub MyDate input Oleaut32.dll v2.1 or earlier expected behavior Oleaut32.dll v 2.2 or later expected behavior 1/1/00 1/1/1 1/1/9 1/1/2000 4/1/98 10/24/29 7/4/30 1/1/1900 1/1/1901 1/1/1909 1/1/2000 4/1/1998 10/24/1929 7/4/1930 1/1/2000 1/1/2001 1/1/2009 1/1/2000 4/1/1998 10/24/2029 7/4/1930 Note that by excluding the quotations in setting the value of MyDate, VBA automatically interprets the date in 4 digit format as it is being entered.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Office Standard 95 7.0 (Swedish)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System Clock | ||
| 12 Aug 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Office 95 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent Note: The below information refers to the code that is shared between Office 95 documents. Please see the individual applications for more detailed information on the product. Prerequisites An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmDescription of how the product handles dates: All dates and times that are displayed or query-able by the user are obtained from the operating system's date and time, stored as fully qualified four-digit year dates and displayed according to user settings in the operating system. Setup has no date sensitivity except in setup file removal. See below for testing implications For VBA and the shared Office object model: All dates and times displayed are obtained from the operating system clock. All dates are stored using a 4-digit year format. A date may be displayed in a 2-digit format (by formatting cells in an Excel worksheet for example) but the value is always stored as a 4-digit year value. Since a common programming language (VBA v4) is used by all applications, date handling for all applications can be tested by testing the VBA intrinsic commands. These intrinsic functions for date handling include: Now () CDate() CVDate() DateValue() Date() Date$() Format() DateAdd() DateDiff() DatePart() IsDate() Day() Month() Weekday() Year() Shared Object Model Methods and Properties Files stored in Office format (.xls, .doc, .ppt etc.) have date properties associated with them. These properties can be manipulated using VBA methods. Objects, Methods, Properties, and Collections possibly affected by Year 2000 Microsoft Office Language Reference Document Properties Object- Property type can be date e.g. msoPropertyTypeDate CreationDate Property LastPrintDate Property LastSaveTime Property PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth Add Method Condition Property FileSearch Object LastModified Property 2-digit shortcut handling: Advanced Find under File/Open allows the entry of 2-digit dates. Beyond Advance Find File, Office shared features support short dates as system display options only. See individual applications for additional information. In Advanced Find, distant future dates have little meaning relative to file creation dates. Therefore, the date is assumed to fall within a range between current year minus 90 years and plus 10 years. For example, in the year 1998 the date range spans from 1908 to 2008. See individual applications for additional shortcut logic. Logic is designed to be appropriate for particular application. The Office Document Properties dialog stores and displays file date information consistent with the 4-digit year format set in the Windows Control Panel Regional Settings. However, the date formatting used in the Custom Document Properties dialog, does not properly recognize two digit years past 1999, so organizations using dates in custom properties should include all four digits of the year when entering them. For VBA and the shared Office object model: In the original configuration, all 2 digit dates were assumed to belong to the current century as defined by the system clock. The logic rules that determine this are included in the oleaut32.dll shared resource file. In any particular computer configuration, this shared resource file may have been updated. This will occur if a browser (Internet Explorer 3.x or greater), Operating System (Windows 95 OEM Service Release 2.5, Windows 98, Windows NT 4, or other Office application is installed or updated using a newer oleaut32.dll file. In this case, the Office95 applications will use 2 digit date handling logic consistent with the oleaut32.dll version. Users should load oleaut32.dll v2.20.4122 or later to the c:\Windows\System (Windows 95) or c:\WINNT\System32 (Windows NT) directories for all affected computers. This will ensure that the date handling characteristics for 2 digit dates are consistent with the date window approach outlined above for all computers. For additional Information please see the VBA Year 2000 Product GuideRecommendations to meet compliance: 1) An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htm-2) See the Year 2000 Product Guide for your computer operating system and install prerequisite updates for Year 2000 compliance. Also see the Product Guide documents for individual Office 95 applications. 3) Set display of short dates to include four digit years, both in your control panel regional settings and in the default display formatting for each application. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data. If it is necessary to use plain text data, it should be saved and manipulated with the full four-digit year. Text values that contain date data should be checked to ensure that they contain the full four-digit year. Data entered or imported into Microsoft Office applications such as Microsoft Word or Microsoft PowerPoint, which do not have data typing in the document format, will be treated as simple text. Those applications should not be used to store dates for which calculations are based (except in the instance of document properties). Standard document properties can be consistently queried and used across all Microsoft Office applications for date queries and calculations, both programmatically and through the user interface, but user-defined custom properties could generate inconsistencies. For VBA and the shared Office object model: User-defined functions are a prime area of date handling errors. A poorly written function may lead to problems. Dates that are stored as strings can also be a problem if there is an error in the information. The VBA language will interpret a string as a date if by rearranging the month/day/year order a valid date can be found. For example, both 3/30/98 (March 30, 1998) and 187/3/1 (March 1, 187) are valid dates even though the month/day/year order have changed. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing across all Microsoft Office products can be conducted safely. Setup maintenance mode (for file removal), the only date sensitive portion of Microsoft Office setup, removes all templates except those installed in recent months. This does not affect Year 2000 compliance, but it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be otherwise. Area SubArea Microsoft’s Testing Summary File Open/Save Dialog Document Properties Document management features include file open/save bringing up the proper "OK to Replace?" confirmation dialog when attempting to save a file after the date/time has been changed; display of dates in results pane of dialog; sorting of dates in results pane of file open/save dialog. Findfast Creation date of index Create an index with the date set to the year 2000. Click Index, create index, select the index mentioned and hit Information. Ensure that the date shown says the year 2000 or 00 depending on the regional settings. Last modified date of index Have Findfast set to update itself every 3 minutes. Set the system date to December 31, 1999, and have it roll over to the year 2000. Verify that updating mechanism for Findfast is not affected. Creation date of file Create a file created on January 1, 2000. Perform a search using an Office App for files created after December 30, 1999, and verify that the file was found. Findfast (cont.) Last modified date of file Create a file last modified on January 1, 2000. Perform a search using an Office App for files last modified after December 30, 1999 and verify that the file was found. Last printed date of file Create a file last modified on January 1, 2000. Perform a search using an Office App for files last modified after December 30, 1999 and verify that the file was found. Custom date property Create a file with a custom date property of January 1, 2000. Perform a search using an Office App for files with that property set to a date later than December 30, 1999 and verify that the file was found. Leap year testing Repeat the above 5 tests using February 29 and 28, 2000, 2001, and 2004, as the dates used. Log file Verify that the log file shows the year 00 for any logs in the year 2000 if the regional settings are set to 2 digit format, and 2000 if the regional settings are set to 4 digit format. Displayed dates Verify that the displayed dates for the creation/last modified dates of the index show 00 for the year 2000 if the regional settings are set to 2 digit format, and 2000 if the regional settings are set to 4 digit format. Setup Complete Install Complete install is a superset of other options. Should be performed on clean machine and on machine with Office version 95 installed with all combinations spanning the turn of the century. Maintenance Mode Remove All For VBA and the shared Office object model: Users testing applications written in VBA should be especially careful to test four main problem areas: User-defined functions: Many applications contain user-defined functions written in VBA to deal with dates in various ways. Many of these functions store date values as strings. Manipulating these values improperly can result in date handling errors that are outside of the scope of the testing that was done at Microsoft. The date usage error described above can cause problems if an error handling routine is meant to catch improperly entered dates. Since VBA rarely generates an error when a string date is used as an input, an error handling routine is unlikely to be called. In this case the proper programming technique would be to validate the data using code instead of relying on an error to signal an improper date. Interactions between computers with varying versions of oleaut32.dll should be tested to ensure that the two digit assumptions built into this system file do not cause problems. Code Example: The following example illustrates the date window in action with various input dates. Depending on the version of the file oleaut32.dll installed, this code will produce varying results. Sub TestDate() Dim MyDate As Date MyDate = "1/1/00" Format MyDate, "mm/dd/yyyy" MsgBox MyDate End Sub MyDate input Oleaut32.dll v2.1 or earlier expected behavior Oleaut32.dll v 2.2 or later expected behavior 1/1/00 1/1/1 1/1/9 1/1/2000 4/1/98 10/24/29 7/4/30 1/1/1900 1/1/1901 1/1/1909 1/1/2000 4/1/1998 10/24/1929 7/4/1930 1/1/2000 1/1/2001 1/1/2009 1/1/2000 4/1/1998 10/24/2029 7/4/1930 Note that by excluding the quotations in setting the value of MyDate, VBA automatically interprets the date in 4 digit format as it is being entered.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Office Standard 97 8.0 (Arabic)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the compliance rating section below | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the compliance rating section below | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the compliance rating section below | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 Aug 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code. The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Why the product is compliant#*: For all Arabic Office 97 applications and with the exception of Outlook 97, if the user enters a date that uses a two-digit year in the Custom tab of the Properties dialog box, the date will be formatted with a value between 1900 – 1999. As an example the user does the following:
The date will appear in the properties list box as 7/5/1900, not 7/5/2000. For information check the Knowledge Base Article Q186261
Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include 4-digit years. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program.Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
| ||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Office Standard 97 8.0 (Chinese - Simplified)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 14 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Q197237.An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to Q172733.Download the Office 97 SR-2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Operational Range for Data: System dependent* Note: The below information refers to the code that is shared between Office 97 documents. Please see the individual applications for more detailed information on the product. Description of how the product handles dates: Dates and times that are displayed or query-able by the user are obtained from the operating system date and time, stored as fully qualified 4-digit year dates and displayed according to the user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See below for testing implications. For VBA and the shared Office object model: Since a common programming language (VBA v5) is used by all applications, date handling for all applications can be tested by testing the VBA intrinsic commands. These intrinsic functions for date handling include:
Year()
All dates and times displayed are obtained from the operating system clock. All dates are stored using long format. A date may be displayed in 2 digit format (by formatting cells in an Excel worksheet, or using the VBA format function, for example) but the value is always carried as a long value. When only given 2 digits, the product assumes the first 2 digits of the year according to the 2-digit rules described below. Files produced by Office97 applications contain date information (DateCreated, DateModified, etc…) which are accessible programmatically. (All files created through normal file commands have 4 digit dates attached ) When only 2 digits are specified for the dates for these attributes, the leading two digits are also assumed according to the 2 digit rule below. Shared Object Model Methods and Properties Files stored in Office format (.xls, .doc, .ppt etc.) have date properties associated with them. These properties can be manipulated using VBA methods. Testing for Y2K has been done to ensure compliance. Objects, Methods, Properties, and Collections possibly affected by Y2K Microsoft Office Language Reference
Code Example: The following example illustrates the date window in action with various input dates. Sub TestDate()
End Sub
Note that by excluding the quotations in setting the value of MyDate, VBA automatically interprets the date in 4 digit format as it is being entered. Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Chinese - Traditional)
| - | ||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| System clock | ||
| 14 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Q197237.An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to Q172733.Download the Office 97 SR-2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR 2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Operational Range for Data: System dependent * Note: The below information refers to the code that is shared between Office 97 documents. Please see the individual applications for more detailed information on the product. Description of how the product handles dates: Dates and times that are displayed or query-able by the user are obtained from the operating system date and time, stored as fully qualified 4-digit year dates and displayed according to the user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See below for testing implications. For VBA and the shared Office object model: Since a common programming language (VBA v5) is used by all applications, date handling for all applications can be tested by testing the VBA intrinsic commands. These intrinsic functions for date handling include: Now ()
CDate()
CVDate()
DateValue()
Date()
Date$()
Format()
DateAdd()
DateDiff()
DatePart()
IsDate()
Day()
Month()
Weekday()
Year()
All dates and times displayed are obtained from the operating system clock. All dates are stored using long format. A date may be displayed in 2 digit format (by formatting cells in an Excel worksheet, or using the VBA format function, for example) but the value is always carried as a long value. When only given 2 digits, the product assumes the first 2 digits of the year according to the 2-digit rules described below. Files produced by Office97 applications contain date information (DateCreated, DateModified, etc…) which are accessible programmatically. (All files created through normal file commands have 4 digit dates attached ) When only 2 digits are specified for the dates for these attributes, the leading two digits are also assumed according to the 2 digit rule below. Shared Object Model Methods and Properties Files stored in Office format (.xls, .doc, .ppt etc.) have date properties associated with them. These properties can be manipulated using VBA methods. Testing for Y2K has been done to ensure compliance. Objects, Methods, Properties, and Collections possibly affected by Y2K Microsoft Office Language Reference
Document Properties Object- Property type can be date eg msoPropertyTypeDate CreationDate Property LastPrintDate Property LastSaveTime Property PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth Add Method Condition Property FileSearch Object LastModified Property
2-digit shortcut handling: System display options only within the shared Office features. See individual applications. The Advanced Find functionality uses a 10-year window from current date to identify the appropriate century since file creation dates far in the future make little sense. Logic across individual applications within Office is designed to be appropriate for each particular application and can be found in their individual product guides. For VBA and the shared Office object model: The first 2 digits are assumed according to a specific rule in cases where only 2 digits are supplied for the date. The rule is:
2 digit dates between 00-29 are assumed to occur in the 21st century (2000-2029). 2 digit dates between 30-99 are assumed to occur in the 20th century (1930-1999).
This interpretation applies to all dates whether the date is used by an intrinsic function, the date is directly entered into an Office program, or the date information is assigned to a file attribute using VBA. For more information see the VBA 5.0 Product Guide. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data. If necessary, plain text data should be saved and manipulated with the full 4-digit year. VBA and ODBC will correctly handle Microsoft Office date typed data. Text values that contain date data should be assured to contain the full 4-digit year. Data entered or imported into Microsoft Office applications such as Microsoft Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text so those applications should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office applications for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For VBA and the shared Office object model: User-defined functions are a prime area of date handling errors. A poorly written function may lead to problems. Dates that are stored as strings can also be a problem if there is an error in the information. The VBA language will interpret a string as a date if by rearranging the month/day/year order a valid date can be found. For example, both 3/30/98 (March 30, 1998) and 187/3/1 (March 1, 187) are valid dates even though the month/day/year order have changed. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing across Microsoft Office products can be conducted safely. OFFCLEAN.DLL, the only date-sensitive portion of Office setup, removes templates except those installed in recent months. This does not affect Year 2000 compliance, but it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be otherwise.
Area
SubArea
Microsoft’s Testing Summary
File
Open/Save Dialog Document Properties
Document management features include file open/save bringing up the proper "OK to Replace?" confirmation dialog when attempting to save a file after the date/time has been changed; display of dates in results pane of dialog; sorting of dates in results pane of file open/save dialog.
Findfast
Creation date of index
Create an index with the date set to the year 2000. Click Index, create index, select the index mentioned and hit Information. Ensure that the date shown says the year 2000 or 00 depending on the regional settings.
Last modified date of index
Have Findfast set to update itself every 3 minutes. Set the system date to December 31, 1999, and have it roll over to the year 2000. Verify that updating mechanism for Findfast is not affected.
Creation date of file
Create a file created on January 1, 2000. Perform a search using an Office App for files created after December 30, 1999, and verify that the file was found.
Findfast (cont.)
Last modified date of file
Create a file last modified on January 1, 2000. Perform a search using an Office App for files last modified after December 30, 1999 and verify that the file was found.
Last printed date of file
Create a file last modified on January 1, 2000. Perform a search using an Office App for files last modified after December 30, 1999 and verify that the file was found.
Custom date property
Create a file with a custom date property of January 1, 2000. Perform a search using an Office App for files with that property set to a date later than December 30, 1999 and verify that the file was found.
Leap year testing
Repeat the above 5 tests using February 29 and 28, 2000, 2001, and 2004, as the dates used.
Log file
Verify that the log file shows the year 00 for any logs in the year 2000 if the regional settings are set to 2 digit format, and 2000 if the regional settings are set to 4 digit format.
Displayed dates
Verify that the displayed dates for the creation/last modified dates of the index show 00 for the year 2000 if the regional settings are set to 2 digit format, and 2000 if the regional settings are set to 4 digit format.
Setup
Complete Install
Complete install is a superset of other options. Should be performed on clean machine and on machine with Office version 95 installed with all combinations spanning the turn of the century.
Maintenance Mode
Remove All
For VBA and the shared Office object model: Users testing applications written in VBA should be especially careful to test three main problem areas:
User-defined functions: Many applications contain user-defined functions written in VBA to deal with dates in various ways. Many of these functions store date values as strings. Manipulating these values improperly can result in date handling errors that are outside of the scope of the testing that was done at Microsoft on the Y2K issue. The date usage error described above can cause problems if an error handling routine is meant to catch improperly entered dates. Since VBA rarely generates an error when a string date is used as an input, an error handling routine is unlikely to be called. In this case the proper programming technique would be to validate the data using code instead of relying on an error to signal an improper date. Applications using the TransferText method in Access should be tested to determine how dates past 1999 are handled. It is preferable to re-write code that contains this method such that dates are transferred using date data types instead of text.
Code Example: The following example illustrates the date window in action with various input dates. Sub TestDate()
Dim MyDate As Date MyDate = "1/1/00" Format MyDate, "mm/dd/yyyy" MsgBox MyDate
End Sub MyDate input
Expected behavior
1/1/00 1/1/1 1/1/9 1/1/2000 4/1/98 10/24/29 7/4/30 2/29/00 2/29/1900
1/1/2000 1/1/2001 1/1/2009 1/1/2000 4/1/1998 10/24/2029 7/4/1930 2/29/2000 error- Type mismatch (1900 not a leap year)
Note that by excluding the quotations in setting the value of MyDate, VBA automatically interprets the date in 4 digit format as it is being entered.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Czech)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Danish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Dutch)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (English)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Finnish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (French)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 14 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (German)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Greek)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Hebrew)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 14 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Why the product is compliant#*: For all Hebrew Office 97 applications and with the exception of Outlook 97, if the user enters a date that uses a two-digit year in the Custom tab of the Properties dialog box, the date will be formatted with a value between 1900 – 1999. As an example the user does the following:
The date will appear in the properties list box as 7/5/1900, not 7/5/2000. For information check the Knowledge Base Article Q186261
Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include 4-digit years. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program.Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Hungarian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Italian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Japanese)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 or the year 2000 software update in Office 97; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (Service Pack 3 or greater is required, though SP 4 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 14 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 and year 2000 software update 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 upgradePrerequisites:
An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to Q172733.Download the Office 97 SR-2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 200 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Note: to install Office 97 SR-2, Office 97 SR-1 is required. Microsoft has prepared a year 2000 software update only for customers who have not installed Office 97 SR-1. You can download this software update from the following site: This update software is the same as the year 2000 software update in Office 97 SR-2. Operational Range for Data: System dependent
Year() All dates and times displayed are obtained from the operating system clock. All dates are stored using long format. A date may be displayed in 2 digit format (by formatting cells in an Excel worksheet, or using the VBA format function, for example) but the value is always carried as a long value.
Code Example: The following example illustrates the date window in action with various input dates. Sub TestDate()
End Sub
Note that by excluding the quotations in setting the value of MyDate, VBA automatically interprets the date in 4 digit format as it is being entered. Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Korean)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 14 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 97 Service Release 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to Q172733.Download the Office 97 SR-2 Patch from http://www.microsoft.com/korea/office/97/sr2.htmThe changes in Office 97 that were made in SR 2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.
* Note: The below information refers to the code that is shared between Office 97 documents. Please see the individual applications for more detailed information on the product. Description of how the product handles dates: Dates and times that are displayed or query-able by the user are obtained from the operating system date and time, stored as fully qualified 4-digit year dates and displayed according to the user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See below for testing implications. For VBA and the shared Office object model: Since a common programming language (VBA v5) is used by all applications, date handling for all applications can be tested by testing the VBA intrinsic commands. These intrinsic functions for date handling include:
Year()
All dates and times displayed are obtained from the operating system clock. All dates are stored using long format. A date may be displayed in 2 digit format (by formatting cells in an Excel worksheet, or using the VBA format function, for example) but the value is always carried as a long value. When only given 2 digits, the product assumes the first 2 digits of the year according to the 2-digit rules described below. Files produced by Office97 applications contain date information (DateCreated, DateModified, etc…) which are accessible programmatically. (All files created through normal file commands have 4 digit dates attached ) When only 2 digits are specified for the dates for these attributes, the leading two digits are also assumed according to the 2 digit rule below. Shared Object Model Methods and Properties Files stored in Office format (.xls, .doc, .ppt etc.) have date properties associated with them. These properties can be manipulated using VBA methods. Testing for Y2K has been done to ensure compliance. Objects, Methods, Properties, and Collections possibly affected by Y2K Microsoft Office Language Reference
Code Example: The following example illustrates the date window in action with various input dates. Sub TestDate()
End Sub
Note that by excluding the quotations in setting the value of MyDate, VBA automatically interprets the date in 4 digit format as it is being entered. Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Norwegian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Polish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Portuguese (Brazil))
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Portuguese)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Russian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Slovak)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Prerequisites: A year 2000 update for Office 97 is available on < ftp://ftp.emwac.cz/pub/office/year2000/sk/of97y2k.EXE>. That update fixes a number of issues previously identified as acceptable deviations in Word, Excel, PowerPoint, Outlook and Office shared components.Operational Range for Data: Component specific* Note: The below information refers to the code that is shared between Office 97 documents. Please see the individual applications for more detailed information on the product. Description of how the product handles dates: Dates and times that are displayed or query-able by the user are obtained from the operating system date and time, stored as fully qualified 4-digit year dates and displayed according to the user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See below for testing implications. For VBA and the shared Office object model: Since a common programming language (VBA v5) is used by all applications, date handling for all applications can be tested by testing the VBA intrinsic commands. These intrinsic functions for date handling include:
Year()
All dates and times displayed are obtained from the operating system clock. All dates are stored using long format. A date may be displayed in 2 digit format (by formatting cells in an Excel worksheet, or using the VBA format function, for example) but the value is always carried as a long value. When only given 2 digits, the product assumes the first 2 digits of the year according to the 2-digit rules described below. Files produced by Office97 applications contain date information (DateCreated, DateModified, etc…) which are accessible programmatically. (All files created through normal file commands have 4 digit dates attached ) When only 2 digits are specified for the dates for these attributes, the leading two digits are also assumed according to the 2 digit rule below. Shared Object Model Methods and Properties Files stored in Office format (.xls, .doc, .ppt etc.) have date properties associated with them. These properties can be manipulated using VBA methods. Testing for Y2K has been done to ensure compliance. Objects, Methods, Properties, and Collections possibly affected by Y2K Microsoft Office Language Reference
System display options only within the shared Office features. See individual applications. The Advanced Find functionality uses a 10-year window from current date to identify the appropriate century since file creation dates far in the future make little sense. Logic across individual applications within Office is designed to be appropriate for each particular application and can be found in their individual product guides. For VBA and the shared Office object model: The first 2 digits are assumed according to a specific rule in cases where only 2 digits are supplied for the date. The rule is:
For more information see the VBA 5.0 Product Guide. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data. If necessary, plain text data should be saved and manipulated with the full 4-digit year. VBA and ODBC will correctly handle Microsoft Office date typed data. Text values that contain date data should be assured to contain the full 4-digit year. Data entered or imported into Microsoft Office applications such as Microsoft Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text so those applications should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office applications for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For VBA and the shared Office object model: User-defined functions are a prime area of date handling errors. A poorly written function may lead to problems. Dates that are stored as strings can also be a problem if there is an error in the information. The VBA language will interpret a string as a date if by rearranging the month/day/year order a valid date can be found. For example, both 3/30/98 (March 30, 1998) and 187/3/1 (March 1, 187) are valid dates even though the month/day/year order have changed. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing across Microsoft Office products can be conducted safely. OFFCLEAN.DLL, the only date-sensitive portion of Office setup, removes templates except those installed in recent months. This does not affect Year 2000 compliance, but it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be otherwise.
Users testing applications written in VBA should be especially careful to test three main problem areas:
Code Example: The following example illustrates the date window in action with various input dates. Sub TestDate()
End Sub
Note that by excluding the quotations in setting the value of MyDate, VBA automatically interprets the date in 4 digit format as it is being entered. Office Standard 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 Office Standard 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
Office Standard 97 8.0 (Slovenian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 97uses 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 Office Standard 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
Office Standard 97 8.0 (Spanish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 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 Office Standard 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
Office Standard 97 8.0 (Swedish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 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 Office Standard 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
Office Standard 97 8.0 (Thai)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to the product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Thai Windows 95, Thai Windows 98, Thai Windows NT 4.0 (no specific SP required) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 25 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Office Standard 97 8.0 (Turkish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to product guides in the table below. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below. 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.Operational Range for Data: Product specific; see the table below. The following table lists products in Office Standard 97, summarizes how they handle dates, and lists their operational ranges. For more information, see the links to specific product guides.
Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://officeupdate.microsoft.com/Articles/sr2fact.htm. The changes in Office 97 that were made in SR-2, including year 2000 updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All year 2000 issues reported as fixed in SR-2 exist in SR-1 and in the base Office 97 product.Common date-handling across all Office programs: Except where noted by a product guide, Office programs get their Year 2000-related date information from core Office code The following information refers to the code that is shared between Office 97 documents. Please see the individual product guides for more information about specific products. Dates and times that are displayed or that can be queried by the user are obtained from the operating system date and time, stored as 4-digit-year dates, and displayed according to user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See "Testing guidelines and recommendations," below, for testing implications. Two-digit shortcut handling: Because file creation dates far in the future make little sense, the Advanced Find functionality uses a 10-year window from the current date to identify the appropriate century. Logic across individual programs within Office is designed to be appropriate for each program and can be found in the individual product guides. The Office Document Properties dialog box stores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Because the date formatting used in the Custom Document Properties dialog box does not properly recognize 2-digit years past 1999, organizations using dates in custom properties should include all 4 digits of the year. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using Visual Basic for Applications (VBA). Common date usage errors: Data exchange between Office programs should avoid the use of plain text data. If necessary, plain text data should be saved and manipulated using the full 4-digit year. VBA and ODBC will correctly handle all Office date typed data. Text values that contain date data should be verified to ensure they contain the full 4-digit year. Data entered or imported into Office programs such as Word or PowerPoint, which do not have data typing in the document format, will be treated as simple text. As a result, those programs should not be used to store dates that calculations are based on (except in the instance of document properties). Standard document properties can be consistently queried and used across all Office programs for date queries and calculations, both programmatically and through the user interface. However, user-defined custom properties could generate inconsistencies. For more information about common date usage errors in a specific program, see the product guide for that program. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing across all Office products can be conducted safely. Offclean.dll--the only date-sensitive portion of Office setup--removes all templates except those installed in recent months. This does not affect Year 2000 compliance; however, it could affect Year 2000 testing because moving the system clock ahead to test could cause more templates to be removed than would be removed otherwise. For program-specific testing guidelines and recommendations, see the product guide for that program.
Office Standard 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 Office Standard 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
OLE Automation Technology (All Languages)
| - | |||||||||||
| None | |||||||||||
| Products using OLE Automation technology including Office 95, Office 97, Visual Basic for Applications, Visual Basic | |||||||||||
| System Clock, Visual Basic runtime, (OLE) Automation Libraries | |||||||||||
| 14 Sep 1999 | |||||||||||
|
The Automation Libraries and the Year 2000 In efforts to improve code efficiency and lower the total cost of ownership for our products, Microsoft has recommended to internal developers to use a common Automation Library for handling dates. Over the years, the library has been updated to reflect changing customer needs and add additional functionality. Updated versions of the library are installed with major product releases such as Microsoft Office, Microsoft Visual Studio and Microsoft Internet Explorer. How do I know if I have the automation library? If you're running Windows 95 or Windows NT 3.51 or later, then you use the automation library. What makes up the automation library? Four files make up the automation library. These files are:
These files are installed either by the operating system or an application. How does the automation library affect year 2000 issues? The automation library contains routines for interpreting 2-digit years and provides a convenient way for applications to create unambiguous (serial) dates. So, many of your applications probably use the automation libraries for date handling. Over the years the automation libraries have been revised with regards to their date formatting behavior:
The cutoff above refers to how dates with 2-digit years are evaluated when the Automation Libraries are asked to covert them into an absolute date. From 2.20.4049 and onward, any 2-digit year that is entered is assumed to lie between 1930 and 2029. The user on those operating systems, starting with version 2.30.4257, can change the date window where the control panel allows it. When the Automation Libraries output a date as a string, the string is also formatted differently depending on which version of the Automation Libraries is being used. Starting with 2.20.4049, dates before 1930 or after the year 2000 will have the year field output as a 4-digit date, even if 2-digit display is the preferred mode in the operating system’s control panel. Starting with 2.30.4257 dates from 1930 to 2029 are output with 2-digit years (if that is the preferred format in the control panel). Here are some examples, where quotes represent input to and output from the Automation Libraries: Starting with Version 2.20.4049: "1/1/30" is interpreted as January 1st, 1930, and January 1st, 1930 is output as "1/1/30". "1/1/29" is interpreted as January 1st, 2029, and January 1st, 2029 is output as "1/1/2029" "1/1/00" is interpreted as January 1st, 2000, and January 1st, 2000 is output as "1/1/2000" "1/1/99" is interpreted as January 1st, 1999, and January 1st, 1999 is output as "1/1/99" Starting with Version 2.30.4257: "1/1/30" is interpreted as January 1st, 1930, and January 1st, 1930 is output as "1/1/30". "1/1/29" is interpreted as January 1st, 2029, and January 1st, 2029 is output as "1/1/29" "1/1/00" is interpreted as January 1st, 2000, and January 1st, 2000 is output as "1/1/00" "1/1/99" is interpreted as January 1st, 1999, and January 1st, 1999 is output as "1/1/99"
How do I know what version of the automation libraries my computer has? Click the Start button, select the Find menu item, and click on "Files or Folders..." In the "Name & Location" tab, type (without quotes) "oleaut32.dll" in the field titled "Named." Select the drive in the "Look in" field that your operating system lives on (usually (C:) ). Click "Find Now." When the file shows up in the box below, right click on the file and select "Properties." Click the right hand tab that says "Version." Name some applications that use automation libraries Microsoft Office 95 and later Microsoft Visual Studio (including Visual C++, Visual Basic, Visual Interdev and custom applications) Microsoft Windows 95, Windows 98, Windows NT Workstation, Windows NT Server Microsoft Internet Explorer What are the implications for the organization with multiple versions of the automation libraries? There are a few year 2000 issues that could result from different users having different versions of the automation libraries. These all involve the interpretation of years entered with only two digits. If your software applications and users enter four digit years, there are no problems. If your users or software are entering 2-digit years, then a scenario where different machines are entering years in different centuries is possible. For example, a data entry department could be running a custom application on both Windows NT 3.51 (without service packs) and on Windows NT 4.0 Workstation. If the users are entering dates like 1/1/10, the NT 3.51 machines could record the date as January 1, 1910 while the NT 4.0 machines may record January 1, 2010. By installing the latest service packs or newer applications (like Microsoft Office 97 or Internet Explorer 4.0), you can assure that your systems have more consistent date handling. For Windows 95 and Windows 98 year 2000 information and updates, see http://computingcentral.msn.com/guide/year2000/msy2k/productinfo/windows.asp For Windows NT year 2000 information and updates, see http://www.microsoft.com/technet/year2k/product/product.asp | |||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
OS/2 1.3 (English)
| - | ||
| None | ||
| None | ||
| Functional RTC/BIOS | ||
| 13 Sep 1999 | ||
|
This document summarizes the results of Year 2000 compliance tests for the OS/2 V1.3 Operating System software package. How OS/2 version 1.3 handles dates: OS/2 version 3.1 rolls over the date from 12-31-1999 to 1-1-2000, OS/2 version 3.1 Backup and Restore utilities:
The OS/2 File Manager SEARCH function does not work with ‘BEFORE’, ‘ON’ and ‘AFTER’ criteria when given a search date of 1-1-2000 or 12-31-35: When given 1-1-2000
When given 12-31-35
On dual boot machines, the DOS boot does not keep the correct date & time from previous OS/2 date & time: When the date in the OS/2 session is set to 12-31-99 and the time is set to 23:59:30 and then the system is booted to DOS, the date may not roll over to 2000 or the time may be incorrect. The following systems produce expected results (i.e. no known issues):
Common date usage errors: OS/2 v1.3 allows the user to make a file’s last modification date earlier than the file’s creation date. Also in OS/2 v 1.3, a file’s last access date can be made earlier than the file’s creation date. General Testing guidelines: Please Note: This information is provided to you as general information and not as an exhaustive testing plan for this product or any other product. The general guidelines are not requirements of Microsoft and are subject to the disclaimer as the end of this document. By providing these general guidelines, Microsoft does not assume any responsibility you may have for planning for the transition to the Year 2000 and makes no representation about what effect following or not following them will have on any liability that may be asserted to arise out of that transition
In general, avoid testing in a production environment because one cannot predict side effects with other products. The following areas can be looked at to verify date handling. Timer rollover with Y2K problem PC bios
Test cases for OS/2 File manager under PM The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
Note that ‘Search’ does not behave as expected on 1-1-2000. Test cases for OS/2 File manager under PM The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
Test cases for OS/2 System Editor E.EXE The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
Test cases for OS/2 utilities under PM The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036
Test cases to verify the day of week under OS/2
Test cases for OS/2 toggles the boot up from DOS and OS/2 The following dates are sugegsted: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036 Note the following issue:
Test cases for OS/2 backup and restore utilities The following dates are suggested for testing: 12-31-98, 1-1-99, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 1-1-2004, 2-28-2004, 2-29-2004, 1-1-2035, 12-31-2035, 12-31-2036 Note unexpected results. The /d option of backup utility does not accept 00 as a valid year, but it does accept 01, 34, 2000, and any two digits except 00. The combination of /b and /a (or /e) options of restore utility doesn’t work correctly when the ranges of years cross year 2000. The restore utility does not restore those backup files that need to be restored. Test cases for OS/2 Lan Manager V2.20 Client connected to Windows NT 4.0 Server The purpose of this test is to verify whether the year 2000 flaw will exist when Lan Manager v2.20 runs on OS/2 v1.3 and is connected to Windows NT4.0 server. The networking card is INTEL EthernetExpress 16TP. The time was always set to be 23:59:00 so that it rolls over to the next date. The testing dates are suggested to be 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 3-1-2000, 2-28-2004, 2-28-2008, 2-28-2012, 12-31-2035, 1-1-2036, 1-1-2079.
The File Manager’s ‘SEARCH…’ does not work as expected with year 2000 date. When a file has last modification date 2-04-92, the search all file with DATE after 1-1-2000. The file with last modification date 2-04-92 shows up on result list. Steps to Reproduce:
The File Manager’s SEARCH does not work as expected on search file with ‘BEFORE’, ‘ON’ and ‘AFTER’ Criteria’s Given search dates with years 2000 date (i.e. 1-1-2000 or 12-31-2000), the ‘BEFORE’, ‘ON’, and ‘AFTER’ searches do not produce expected results.
Steps to Reproduce:
The File Manager’s SEARCH does not work as expected on search file with year 2035 date. Given search date with years 12-31-35 date, the search function does not work on ‘BEFORE’, ‘ON’, and ‘AFTER’.
Steps to Reproduce: 1. Create files with dated 12-31-98, 12-31-99, 1-1-2000, 2-28-2000, 2-29-2000, 1-1-2004, 12-31-35, 12-31-36 under one DIRECTORY (for easily spot the result) 2. Go to File Manager, Click File menu item, and then click search … 3. Select ‘DATE’ under search on property, Press OK button 4. Key in 12-31-2035 for last modification, under correct search directory and check ‘BEFORE’ radio button, do search, and then see result list that does not include all files with dated before 12-31-35 . 5. Key in 12-31-2035 for last modification under correct search directory and check ‘ON’ radio button, do search, and then see ‘Cannot files or directories that match the search criteria’ (PMV1070) 6. Key in 12-31-2035 for last modification under correct search directory and check ‘AFTER’ radio button, do search and then the result list include those files with dated before 12-31-2035. The DOS boot won’t keep the correct of date & time from previous OS2 date & time. When OS2 was installed as dual boot, in the OS2 Session, set the date to 12-31-99 and the time to 23:59:30. Then type boot /dos and respond Yes to boot from DOS. After DOS is up, check the date and time. Sometimes, it shows 1980 for the date. When date is right 1-1-2000, the time is wrong. It shows time 12:00:03a when the correct time is 00:00:03. Steps to Reproduce: 1. Install OS2 under dual boot with DOS 2. Under OS/2 window or full screen mode, or DOS session, set date to be 12-31-99 and time 23:59:30 Type boot /dos and respond yes to boot from DOS 3. After Boot up from DOS, then check the date and time 4. Sometimes, it displays 1980; other times it displays 1-1-2000 for the date.
The Backup /D option command does not take 00 as legal year input parameter. Steps to Reproduce: 1. Create file with date after year 2000. 2. Under the OS/2 window or full screen mode, runs Backup *.* a: /D:1-1-00 3. OS/2 Backup utility does not accept ‘00’ as a valid year. The message " SYS1036: The system cannot accept the dated entered" was shown on screen. The Restore /b and /e option command does not work as expected when backup files are mixed with the 19xx and 2000 dates. The restore utility doesnot restore the correct files from backup files with /b and /e options. Steps to Reproduce: Create the following files with specified date and time. Date: 12-31-99 time: 9:0:0 t9909.txt Date: 12-31-99 time: 11:0:0 t9911.txt Date: 12-31-99 time: 14:0:0 t9914.txt Date: 12-31-99 time: 16:0:0 t9916.txt Date: 1-1-2000 time: 9:0:0 t0009.txt Date: 1-1-2001 time: 8:0:0 t0108.txt Date: 1-1-2001 time: 14:0:0 t0114.txt Backup all files into diskette by entering backup *.* a: /s Run restore a: /b:1-1-2000 /e:11:0:0 Only files t0009.txt and t9909.txt are restored; t9911.txt, t9914.txt, and t9916.txt files are not restored.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook (Mac) 8.XX (English)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| Apple System 7.1 or higher, Macintosh operating system 7.6.1 or higher; Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater. | ||
| Operating System Clock | ||
| 11 Jan 1999 | ||
|
Product: Microsoft Outlook for Macintosh, Exchange Server Edition Release dates: October 1997, July 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 2 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, etc.
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
Outlook (Mac) 8.XX (French)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| Apple System 7.1 or higher, Macintosh operating system 7.6.1 or higher; Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater. | ||
| Operating System Clock | ||
| 08 Jan 1999 | ||
|
Product: Microsoft Outlook for Macintosh, Exchange Server Edition Release dates: October 1997, July 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 2 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, etc.
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
Outlook (Mac) 8.XX (German)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| Apple System 7.1 or higher, Macintosh operating system 7.6.1 or higher; Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater. | ||
| Operating System Clock | ||
| 08 Jan 1999 | ||
|
Product: Microsoft Outlook for Macintosh, Exchange Server Edition Release dates: October 1997, July 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 2 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, etc.
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
Outlook (Mac) 8.XX (Japanese)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| Apple System 7.1 or higher, Macintosh operating system 7.6.1 or higher; Exchange Server 4.0 Service Pack 5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater. | ||
| Operating System Clock | ||
| 08 Jan 1999 | ||
|
Product: Microsoft Outlook for Macintosh, Exchange Server Edition Release dates: October 1997, July 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 2 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, etc.
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
Outlook (Win 3.1) 8.XX (English)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| Windows 3.1; Exchange Server 4.0 Service Pack5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater. | ||
| Operating System Clock | ||
| 11 Jan 1999 | ||
|
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 Outlook for Windows 3.1 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 2 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, etc.
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
Outlook (Win 3.1) 8.XX (French)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| Windows 3.1; Exchange Server 4.0 Service Pack5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater. | ||
| Operating System Clock | ||
| 08 Jan 1999 | ||
|
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 Outlook for Windows 3.1 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 2 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, etc.
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
Outlook (Win 3.1) 8.XX (German)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| Windows 3.1; Exchange Server 4.0 Service Pack5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater. | ||
| Operating System Clock | ||
| 08 Jan 1999 | ||
|
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 Outlook for Windows 3.1 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 2 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, etc.
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
Outlook (Win 3.1) 8.XX (Japanese)
| 01 Jan 1980 - 31 Dec 2035 | ||
| None | ||
| Windows 3.1; Exchange Server 4.0 Service Pack5 or Exchange Server 5.0 Service Pack 2 or greater, Exchange Server 5.5 Service Pack 2 or greater. | ||
| Operating System Clock | ||
| 08 Jan 1999 | ||
|
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 Outlook for Windows 3.1 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 2 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, etc.
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
Outlook 2000 9.0 (Arabic)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Basque)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Chinese - Simplified)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Chinese - Traditional)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Croatian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Czech)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Danish)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Dutch)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (English)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.This document applies to Outlook 2000 and its Team Folders Kit component. How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (English Australian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (English British)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Estonian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Finnish)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (French)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (German)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Greek)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Hebrew)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Hindu)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Hungarian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Italian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Japanese)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System Clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Korean)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Latvian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Lithuanian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Norwegian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Pan-Chinese)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Polish)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Portuguese (Brazil))
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Portuguese)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Romanian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Russian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Serbian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Slovak)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Slovenian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Spanish)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Swedish)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Thai)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 2000 9.0 (Turkish)
| 01 Apr 1601 - 31 Aug 4500 | ||
| None | ||
| Windows 95, Windows 98, or Windows NT 4.0 with Service Pack 3 or later | ||
| System clock | ||
| 15 Sep 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Outlook 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.How the product handles dates:
2-digit shortcut handling: Date entry fields parse and accept 2-digit year inputs that follow the format specified on the Date tab in Regional Settings. On Windows 95 and Windows NT 4.0 operating systems, Outlook interprets 2-digit-year entries as a year in 1930 through 2029. On the Windows 98 operating system, Outlook respects the year range setting specified by the user on the Date tab in Regional Settings. Outlook interprets 2-digit year entries as a year in the specified range. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date; the Inbox Assistant and Out of Office Assistant’s Advanced rule settings use the range of 1980-2079; and the Import/Export Wizard operates through the year 2035. Common date usage errors:
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Microsoft recommends developers use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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 date fields and Long date fields on custom Exchange Forms Designer 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 information about Visual Basic 4.0 compliance issues.See the Microsoft Exchange Server product guide for information about server compliance issues.See the Microsoft Internet Explorer product guide for information about Internet Explorer compliance issues.Outlook 2000 uses a number of Microsoft Office 2000 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 97 (Arabic)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Outllib.dll version 8.01QFE-E is required for Year 2000 compliance. | ||
| Arabic Windows 95 or later, Arabic Windows NT4 or later (no specific SP is required, (although Service Pack 2 is recommended). | ||
| System clock | ||
| 28 Oct 1999 | ||
|
Prerequisite: Outllib.dll version 8.01QFE-E is required for Year 2000 compliance. This update can be downloaded from http://www.microsoft.com/middleeast/support/download.stmHow the product handles dates:
Two-digit shortcut handling: For 2-digit year entries, Outlook uses a window that includes a period 30 years prior to and 70 years after a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to interpret what the user meant. An error is generated only if no valid date can be determined. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields use a window that includes a period 95 years prior to and 5 years after the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing 2-digit-year information from text files into Outlook may result in some years being interpreted incorrectly. For more information, see Microsoft Knowledge Base article Q197237.
Common date usage errors:
Without the Outlook 97 QFE update, there are two areas in which this parsing behavior commonly manifests itself: One area is in the user interface where date entries are parsed. For example, in the calendar module, if the user clicks Go to Date on the Go To menu and then types 12/25/99, Outlook takes the user to December 25, 2099. Another area is in custom forms that make calculations based on dates. When a date is entered and displayed using only 2-digit years, there is no visual clue that the date has been parsed to the correct century. For example, suppose there is a form that allows a user to enter a purchase date and then uses script to calculate a warranty date that is one year in the future. If this form shows only 2 digits for the year entered and the user enters 12/1/99 as the purchase date, the warranty date is calculated as 12/1/2100 because the purchase date was parsed as 12/1/2099. Because the form shows only 2-digit years for dates, both dates appear to be correct and display as 12/1/99 and 12/1/00. Internally, however, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated Outllib.dll version 8.01QFE-E that is available in the Outlook 97QFE update changes the parsing behavior to the expected results.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features--such as appointments and tasks--that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Developers should use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If using Outlook to send or view Microsoft Exchange Forms Designer custom forms, note that 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 Exchange Forms Designer forms are stored as string values. These custom date fields will not sort or filter correctly. For information about Visual Basic 4.0 compliance issues, see the Visual Basic (16-bit) product guide.See the Exchange Server-Enterprise product guide or the Exchange Server-Standard product guide for information about server compliance issues.See the Internet Explorer (16-bit) product guide or the Internet Explorer (32-bit) product guide for information about Internet Explorer compliance issues.Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Chinese - Simplified)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0 - 8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update. | ||
| Windows 95, Windows 98 or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 (no specific Service Pack is required, though Service Pack 2 or higher is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.How the product handles dates:
If the user has Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from Office 97 SR-2 to properly handle short dates when scheduling events that span the century boundary. If the user has Microsoft Outlook 97 Service Release 2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then this update is not needed since the fix is already included in those versions of Outlook.
Two-digit shortcut handling: For 2-digit year entries, Outlook employs a date window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the system’s short date format, a standard algorithm is used to attempt to discern what the user meant. Only when a valid date can not be interpreted is an error message generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors:
The updated OUTLLIB.DLL version 8.04 from Office 97 SR-2 changes the parsing behavior to the expected results.
Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If Outlook is used to send or view Microsoft Exchange Forms Designer (EFD) custom forms, please note that 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 2-digit year and 4-digit date fields on custom Exchange Forms Designer forms are stored as string values. These custom date fields will not sort or filter as expected. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. See the Microsoft Exchange Server Product Guide for details on server date handling characteristics. If Microsoft Internet Explorer 3.0x is installed, please see the Internet Explorer Product Guide for details on Internet Explorer date handling characteristics. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Chinese - Traditional)
| 01 Apr 1601 - 31 Aug 4500 | |||
| Office 97 Service Release 2 for Outlook 8.0 - 8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | |||
| Windows 95, Windows 98, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 (no specific Service Pack is required, though Service Pack 2 or higher is recommended) | |||
| Operating System Clock | |||
| 28 Oct 1999 | |||
| |||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Outlook 97 (Czech)
| 01 Jan 1601 - 31 Dec 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0 - 8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| 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 | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Danish)
| 01 Jan 1601 - 31 Dec 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0 - 8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| 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 | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Dutch)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0 - 8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (English)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0 - 8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook. 2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Finnish)
| 01 Jan 1601 - 31 Dec 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| 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 | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (French)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (German)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Greek)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outllok 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Hebrew)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Outllib.dll version 8.01QFE-E is required for Year 2000 compliance. | ||
| Hebrew Windows 95 or later, Hebrew Windows NT4 or later (no specific SP is required, (although Service Pack 2 is recommended). | ||
| System clock | ||
| 28 Oct 1999 | ||
|
Prerequisites: Outlook 97: English interface: http://www.microsoft.com/israel/downloads/eoutlook97qfe1.exeOutlook 97: Hebrew interface: http://www.microsoft.com/israel/downloads/loutlook97qfe1.exe
Note on Outlook 97 software update: there are no versions higher than 8.01 of the file outllib.dll – the update itself changes the version into 8.01qfe-l or 8.01qfe-e. An explanation and a link to download the above Hebrew software updates is available at http://www.microsoft.com/israel/support/support_news.html.How the product handles dates:
Two-digit shortcut handling: For 2-digit year entries, Outlook uses a window that includes a period 30 years prior to and 70 years after a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to interpret what the user meant. An error is generated only if no valid date can be determined. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields use a window that includes a period 95 years prior to and 5 years after the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing 2-digit-year information from text files into Outlook may result in some years being interpreted incorrectly. For more information, see Microsoft Knowledge Base article Q197237.
Common date usage errors:
Without the Outlook 97 QFE update, there are two areas in which this parsing behavior commonly manifests itself: One area is in the user interface where date entries are parsed. For example, in the calendar module, if the user clicks Go to Date on the Go To menu and then types 12/25/99, Outlook takes the user to December 25, 2099. Another area is in custom forms that make calculations based on dates. When a date is entered and displayed using only 2-digit years, there is no visual clue that the date has been parsed to the correct century. For example, suppose there is a form that allows a user to enter a purchase date and then uses script to calculate a warranty date that is one year in the future. If this form shows only 2 digits for the year entered and the user enters 12/1/99 as the purchase date, the warranty date is calculated as 12/1/2100 because the purchase date was parsed as 12/1/2099. Because the form shows only 2-digit years for dates, both dates appear to be correct and display as 12/1/99 and 12/1/00. Internally, however, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated Outllib.dll version 8.01QFE-E that is available in the Outlook 97 QFE update changes the parsing behavior to the expected results.
Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features--such as appointments and tasks--that use the current date as reference dates. Note that reminders for future appointments might be set off during this testing and will not renotify when the date is set back. Additionally, users should enter dates using 4-digit-year information instead of using a truncated 2-digit year format. Developers should use these specific year formats on form controls to help ensure that the correct date is entered and recorded. If using Outlook to send or view Microsoft Exchange Forms Designer custom forms, note that 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 Exchange Forms Designer forms are stored as string values. These custom date fields will not sort or filter correctly. For information about Visual Basic 4.0 compliance issues, see the Visual Basic (16-bit) product guide.See the Exchange Server-Enterprise product guide or the Exchange Server-Standard product guide for information about server compliance issues.See the Internet Explorer (16-bit) product guide or the Internet Explorer (32-bit) product guide for information about Internet Explorer compliance issues.Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Hungarian)
| 01 Jan 1601 - 31 Dec 4500 | ||
| Office 97 Service Release 2 for Outllook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| 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 | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Italian)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Japanese)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 or the year 2000 software update in Office 97 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 (Service Pack 3 or greater is required, though SP 4 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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 Year 2000 issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage: Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook. 2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Korean)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 (no specific Service Pack is required, though Service Pack 2 or higher is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at http://www.microsoft.com/korea/office/97/sr2.htmThe Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.How the product handles dates:
If Outlook 97 version 8.0, 8.01, 8.02 or 8.03 is being used, obtain the Office 97 SR-2 Patch to properly handle short dates (years represented in 2 digits) when scheduling events that span the century boundary. If the user has Microsoft Outlook 97 Service Release-2 (version 8.04) or Microsoft Outlook 98 (version 8.5) this update is not needed since the fix is already included in those versions of Outlook. When using the Gregorian calendar, Outlook employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field’s reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. The Korean Emperor Era calendar is different from the Gregorian calendar by 2333 years. The current year is the Gregorian year + 2333. For example, Gregorian 1999 is Emperor Era year 4332. When using the Korean Emperor Era calendar, Outlook accepts 4-digit year entries in the operational range: years 3934 through 6833 (1601 through 4500 by the Gregorian calendar). In addition, it also accepts 1601 through 2099 and converts them to Korean Emperor years 3934 through 4432. Two-digit year entries are assumed to be in the 4300’s. Note that the Import/Export Wizard only accepts dates in the Gregorian calendar format. Two-digit shortcut handling: To interpret 2-digit year entries while using the Gregorian calendar, Outlook employs a date window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the system’s short date format, a standard algorithm is used to attempt to discern what the user meant. Only when a valid date can not be interpreted is an error generated. To interpret 2-digit year entries while using the Korean Emperor Era calendar, Outlook assumes the 2-digit entry is in the 4300’s. Entries 00 through 99 map to 4300 through 4399, which correspond to years 1967 through 2066 in the Gregorian calendar. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237. Common date usage errors:
The updated OUTLLIB.DLL version 8.04 from Office 97 SR-2 changes the parsing behavior to the expected results.
Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely.
The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. Additionally, users should enter dates using 4-digit year information instead of using a truncated 2-digit year format. Furthermore, developers should use these specific year formats on form controls to help ensure the correct/desired date is entered and recorded. If Outlook is used to send or view Microsoft Exchange Forms Designer (EFD) custom forms, please note that 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 2-digit year and 4-digit date fields on custom Exchange Forms Designer are stored as string values. These custom date fields will not sort or filter as expected. Please see the Visual Basic (16-bit) Product Guide for details on Visual Basic 4.0 compliance issues. See the Microsoft Exchange Server Product Guide for details on server date handling characteristics. If Microsoft Internet Explorer 3.0x is installed, see the Internet Explorer Product Guide for details on Internet Explorer date handling characteristics. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Norwegian)
| 01 Jan 1601 - 31 Dec 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| 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 | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Polish)
| 01 Jan 1601 - 31 Dec 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| 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 | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Portuguese (Brazil))
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0 - 8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update. | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Portuguese)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Russian)
| 01 Jan 1601 - 31 Dec 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| 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 | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Slovenian)
| 01 Jan 1601 - 31 Dec 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| 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 | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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
Outlook 97 (Spanish)
| 01 Apr 1601 - 31 Aug 4500 | ||
| Office 97 Service Release 2 for Outlook 8.0-8.03 users and O97dtfix.exe for the Outlook 97 Import and Export update | ||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||
| Operating System Clock | ||
| 28 Oct 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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: OUTLLIB.DLL version 8.04 for Outlook 8.0 - 8.03 users. This patch is available in Office 97 SR-2, which can be downloaded at 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. This issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.The Microsoft Outlook Support for Lotus cc: Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Description of how the product handles dates: Storage. Dates in Outlook 97 are stored and manipulated as full dates. Dates are integral to the product's operation. The system clock is used for current date and time data. Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in the Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. Parsing on date entry. Outlook 8.0x employs a two-digit date window that spans from 30 years prior to and 70 years forward from a reference date. Each date field's reference date is either the current date or a related date field. The date range for printing an Outlook calendar is limited to 30 years prior to and 70 years forward from the current date. If you are using Outlook 97 version 8.0, 8.01, 8.02 or 8.03, obtain the 8.04 version of OUTLLIB.DLL from the Office 97 SR-2 Patch to properly handle short dates when scheduling events that span the century boundary. If you are using Microsoft Outlook 97 SR-2 (version 8.04) or Microsoft Outlook 98 (version 8.5.5104.6) then you do not need this update since the fix is already included in those versions of Outlook.
2-digit shortcut handling: For 2-digit year entries, Outlook employs a window that includes 30 years back and 70 years forward from a reference date. If a date is entered that does not match the systems short date format, a standard algorithm is used to attempt to discern what the user meant. Only if no valid date can be made is an error generated. Certain features in Outlook are designed to use different parsing algorithms that better fit their particular context. The Birthday and Anniversary fields employ a window that includes 95 years back and 5 years forward from the current date, while the Inbox Assistant and Out of Office Assistant's Advanced rule settings use the range of 1980-2079. Importing or exporting text files with dates formatted with two-digit years may result in some years being designated in the wrong century. For more information on these issues and to download the 097dtfix update please see Knowledge Base article Q197237.Common date usage errors: 1. Outlook originally parsed dates that are entered with 2 digit year components in an unexpected way. If you enter 12/25/99 into a date field, the date will be parsed and stored as 12/25/2099 instead of 12/25/1999. This behavior has been resolved with the patch indicated below. There are two areas of Outlook in which this parsing behavior commonly manifests itself: Several places in the Outlook User Interface parse date entries and will show the unexpected behavior. For example, in the calendar module, if you choose "Go To Date" from the Go menu and type in "12/25/99", Outlook will take you to the day 12/25/2099. Because two digit years are parsed in an unexpected way, if you have custom forms that make calculations based on dates, these calculations may appear to be incorrect. When a date is entered and displayed using only 2 digit years, there is no visual clue that the date has been parsed to the next century. For example, suppose you have a form that allows a user to enter a purchase date, and then uses script to calculate a warranty date 1 year in the future. If this form only shows two digits for the year entered, then the user can type 12/1/99 in the purchase date and the warranty date is calculated as 12/1/2100. This is because the original date was parsed as 12/1/2099. Since the form only shows 2 digits years for dates, both dates APPEAR to be correct and display as 12/1/99 and 12/1/00. Internally, the dates are stored and evaluated as 12/1/2099 and 12/1/2100. The updated OUTLLIB.DLL version 8.04, available in the Office 97 SR-2 Patch, changes the parsing behavior to the expected results. 2. For end-to-end compliance when using Outlook 97 as your e-mail client, you need to use a Year 2000 compliant mail server, including Exchange Server 4.0 SP5 or Exchange Server 5.0 SP2 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, etc. 3. The Microsoft Outlook Support for Lotus cc:Mail from the Outlook 97 ValuPack is Year 2000 compliant only with the update obtained from the Office 97 SR-2 Patch. The resolved issue is simply that 2-digit shortcuts were assumed to be 19xx dates. Testing guidelines and recommendations: In general, avoid testing in a production environment because one cannot predict side effects with other non-compliant products. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. The system clock should be advanced to future dates to properly test features, such as appointments and tasks that use the current date as reference dates. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.Additionally, users should enter dates using 4-digit year information instead of using the truncated 2-digit year format. Furthermore, developers should use 4-digit year formats on form controls to help ensure the correct/desired date is entered and recorded. If you use Outlook to send or view Microsoft Exchange Forms Designer custom forms, please note that 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. See the Microsoft Exchange Server Product Guide for details on server compliance issues. If you install Microsoft Internet Explorer 3.0x, see the Internet Explorer Product Guide for details on Internet Explorer compliance issues. Outlook 97 uses a number of Microsoft Office 97 shared files for the implementation of task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Outlook 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. | |
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.  | ||