Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Office Professional 95 7.0 (Hebrew)
| - | ||
| PP7TRANS.DLL version 7.07 | ||
| Windows 95 | ||
| System clock | ||
| 29 Jul 1999 | ||
|
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 Hebrew 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 Two-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 Guide
Recommendations to meet compliance: 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. The above test need to be conducted with System Calendar set to Gregorian and Hebrew Lunar. 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. Set the system date to the Hebrew Lunar date 22 Tevet 5760 - equivalent to December 31, 1999, and have it roll over to the year 2000. Revert the Calendar back to Gregorian and make sure the updating mechanism of 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. Set the system date to Hebrew Lunar. Use the same file above. Perform a search using an Office App for files created after 21 Tevet 5760 – equivalent to December 30, 1999. Make sure 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. Set the System Calendar to Hebrew Lunar. Create a file last modified on 23 Tevet 5760 - equivalent to January 1, 2000. Perform a search using an Office App for files last modified after 21 Tevet 5760 – equivalent to December 30, 1999. Make sure 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. Switch the system date to Hebrew Lunar. Create a file last printed on 23 Tevet 5760. Perform a search using an Office App for files last modified after 21 Tevet, 5760. Verify 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. Switch System Calendar to Hebrew Lunar. Use the same file you created. Perform a search using an Office App for files with that property set to a date later than 21 Tevet 5760 Hebrew. 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 Professional 95 7.0 (Hungarian)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 24 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.
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.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. * 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. Description 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:
Microsoft Office Language Reference Document Properties Object- Property type can be date e.g. msoPropertyTypeDate
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
End Sub
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 95 7.0 (Italian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 16 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 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.
Microsoft Office Language Reference Document Properties Object- Property type can be date e.g. msoPropertyTypeDate
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
End Sub
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 95 7.0 (Japanese)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System clock | ||
| 23 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 Japanese by providing software updates for identified issues through January 1, 2001, except for the existing Emperor Dating System issues. Newer Service Packs are also to be maintained at least as Compliant*# with the same Emperor Dating System exception coupled with intent to fix other identified issues, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.An Office 95 Year 2000 update is now. For more detailed information and to download this update please go to http://www.microsoft.com/japan/Office/OfficeFreeStuff/Office/O95y2k/.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. Description 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) 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. 2) 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 Professional 95 7.0 (Korean)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 Aug 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Prerequisites
Recommendations:
Description 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:
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
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
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 Guide 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.
Users testing applications written in VBA should be especially careful to test four main problem areas:
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()
End Sub
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 95 7.0 (Norwegian)
| - | ||||||||||||||||||||
| 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.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.htm.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 95 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526 th day in the century.Formatting. When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (refers to a 2-digit year entry), then even when the user types a YYYY (refers to a 4-digit year entry) date, it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown. Leap Year. Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)2-digit shortcut handling: What are the acceptable deviations? Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q180159 for more information.)The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q180159 for more information.)Using a format such as "Dec 98" will break at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Microsoft Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates. Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025. Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2Y format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Excel within your organization.
Additional Testing Instructions Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy". Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test. Set the system clock to 11:59 p.m. December 31, 1999. Start Microsoft Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Excel recognizes the year 2000 as a leap year: Start Microsoft Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice that Microsoft Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.) | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 95 7.0 (Polish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 16 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 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/poland/downloadDetails/O95y2k.htm..
Microsoft Office Language Reference Document Properties Object- Property type can be date e.g. msoPropertyTypeDate
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
End Sub
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 95 7.0 (Portuguese (Brazil))
| - | |||||||||||||||||||||||
| Office 95 Year 2000 Software Update | |||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | |||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||
| 18 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 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/Brasil/downloadDetails/O95y2k.htm.Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
| |||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 95 7.0 (Russian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 18 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 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/rus/downloadDetails/O95y2k.htm.
Microsoft Office Language Reference Document Properties Object- Property type can be date e.g. msoPropertyTypeDate
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
End Sub
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 95 7.0 (Slovenian)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PP7TRANS.DLL version 7.07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 20 Jul 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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.An Office 95 Year 2000 software update will be available in June 1999 that will correct known Year 2000 related issues in the applications used in Office 95. For specific issues remediated by this software update see http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htm
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:
Microsoft Office Language Reference Document Properties Object- Property type can be date e.g. msoPropertyTypeDate
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
End Sub
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 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 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.
Microsoft Office Language Reference Document Properties Object- Property type can be date e.g. msoPropertyTypeDate
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
End Sub
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 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 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.
Microsoft Office Language Reference Document Properties Object- Property type can be date e.g. msoPropertyTypeDate
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
End Sub
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 97 8.0 (Arabic)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific; see the table below. The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 2-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 Professional 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 Professional 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 Professional 97 8.0 (Chinese - Simplified)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5; 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 01 Jul 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 http://support.microsoft.com/support/kb/articles/Q172/7/33.asp.Download the Office 97 Service Release (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 software 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 97 8.0 (Chinese - Traditional)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 01 Jul 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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 http://support.microsoft.com/support/kb/articles/Q172/7/33.asp.Download the Office 97 Service Release (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 software 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Professional 97 8.0 (Czech)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Danish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Dutch)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (English)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Finnish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (French)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (German)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Greek)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table below.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 Professional 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 Professional 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 97Microsoft 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 Professional 97 8.0 (Hungarian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Italian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Japanese)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 or the year 2000 software update in Office 97 and Microsoft Jet 3.5 Update; Outlook 97 Year 2000 Software 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) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 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 http://support.microsoft.com/support/kb/articles/Q172/7/33.asp.Download the Office 97 Service Release 2 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. 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.
* 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.
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 Professional 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 Professional 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 Professional 97 8.0 (Korean)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Micorosft Jet 3.5 Update; 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 http://support.microsoft.com/support/kb/articles/Q172/7/33.asp.Office 97 Service Release (SR) 2 is required for Year 2000 compliance. SR-2 can be Download from http://www.microsoft.com/korea/office/97/sr2.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 reported as fixed in SR2 exist in SR1 and in the base Office 97 product.
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: All dates and times that are displayed or query-able by the user are obtained from the operating system date and time, stored as 4-digit year dates and displayed according to the user settings in the operating system. Setup has no date sensitivity except in the file removal DLL. See below for testing implications. 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 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. The Office Document Properties dialog stores and displays file date information consistent with the long date 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. This problem is quite apparent and easily corrected in the user interface. It does not occur when saving custom document properties using VBA. 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 all 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. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other non-compliant products. Interoperability testing across all Microsoft 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, 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.
Office Professional 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 Professional 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 Professional 97 8.0 (Norwegian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Micorosft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Polish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Portuguese (Brazil))
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Portuguese)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Micorosft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Russian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Micorosft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Slovak)
| - | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Year 2000 Software Update | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SPis 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>. This update resolves a number of issues previously identified as acceptable deviations in Word, Excel, Access, PowerPoint, Outlook and Office shared components.
Office Professional 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 Professional 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 Professional 97 8.0 (Slovenian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Spanish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; Outlook 97 Year 2000 Software | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Swedish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 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 psecific SP required) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Product specific, see the links to the 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 Professional 97 8.0 (Turkish)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and Microsoft Jet 3.5 Update; 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 belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Professional 97 8.0 (Vietnamese)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Vietnamese Windows 95 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 23 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Operational Range for Data: Product specific, see the table belowProduct 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.The following table lists products in Office Professional 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.Office 97 Professional ValuPak Content: File Viewers: The Word, Excel, Snapshot (Access) and PowerPoint viewers included in the Microsoft Office Professional ValuPak have been tested for year 2000 compliance. The PowerPoint 4 viewer makes use of the PowerPoint 7 translator. That translator is updated with Office SR-2 to correctly display two digit years. There are no other known issues. Avery Label Wizard: See http://www.avery.com/resource_center/faq_recSel.html?filename=/disk2/faqs/FAQ0014.html for current information regarding the Avery Label Wizard.Lotus cc:Mail support: Microsoft Outlook Support for Lotus cc: Mail requires an update obtained from Office 97 SR-2. Outlook Import/Export filters: See Outlook 97 Product Guide for current information and availability of updates. MS Camcorder: No date handling issues. Content files: Animated GIFs; animated cursors; additional help files; sounds; additional templates and forms; backgrounds and textures. No date handling issues. Wizards (various): No date handling issues. Word Converter (including Far East document converters and Word 97 converter): No date handling issues. Software Patches (various): No date handling issues. Office 97 Upgrade Wizard: Offclean.dll 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. See also the following Product Guides: Internet Explorer (32 bit), ODBC Core Components, Microsoft Data Access Components, ActiveMovie.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 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 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 Professional 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 Professional 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 Small Business Edition 97 (Canadian 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 Small Business Edition 97 (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. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 Small Business Edition 97 (English Australian)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 Small Business Edition 97 (English British)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2; Out;look 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 Small Business Edition 97 (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. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 Small Business Edition 97 (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. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 Small Business Edition 97 (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. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 Small Business Edition 97 (Korean)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 and the Small Business Solution software update for Korean; Outlook 97 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4.0 Service Pack 4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: System dependent This information applies to Office 97 Small Business Edition Solution (Korean) 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 4-digit year dates and displayed according to the user settings in the operating system, except for the basic date setting. Office 97 Small Business Solution displays 4-digit year dates for basic date setting as a duration setting. Two-digit shortcut handling: Small Business Solution treats numbers 0 - 29 as 20xx (2000-2029) and 30 - 99 as 19xx (1930-1999). Prerequisites: In Outlook 97, importing 2-digit year information from text files is compliant with the update referenced in the following Microsoft Knowledge Base article 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.The Office 97 Service Release 2 software update must be downloaded from http://www.microsoft.com/korea/office/97/sr2.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.The Small Business Solution software update for Korean must be downloaded from http://www.microsoft.com/korea/office/sbe/patch.htmlIssues resolved with the Small Business Solution software update: Flexible fields in Small Business Solution software update: Both the graduation date field in the employee education section and the acquisition date field in the employee license section are flexible field. These fields accept data as a string and do not use it for calculation. Users can insert any format of data and these fields will not convert inserted data into date data. Testing guidelines and recommendations: The date fields are listed below. For testing, users should test 2 cases. First, set the date format to 4-digits. Next check the date fields in the list. Then check 2-digit formats. Users can set the date format using regional setting in control panel.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 Small Business Edition 97 (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. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 Small Business Edition 97 (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. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 Small Business Edition 97 (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. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.Operational Range for Data: Product specific, see the table below. The following table lists products in Office Small Business Edition 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. For Direct Mail Manager In the few places that have dates, 4-digit years are used. Other than the current time/date for the list broker password, Direct Mail Manager stores the date of verification for each address in the standard Access/Jet date format. There is a field in which the user can enter either a 2- or 4-digit year, however no processing takes place. With installation of Office 97 Service Release 2, a 2-digit year date from the Dial-A-Zip process changes to 4 digits immediately after it is read. For Small Business Financial Manager Dates are imported into tables via Excel Visual Basic for Applications (VBA). The user interface also allows the user to select a date (January 1999, for example) from a list. In pre-SR-2 versions of Small Business Financial Manager, when a string like "05-03" was passed to the VBA format function in an "mmmm yyyy" format, it could return an unexpected date (for example, May 1997). This issue is resolved in the SR-2 release by passing fully qualified dates like "05-2003" instead of 2-digit-year dates. 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. 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, 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. 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 (Macintosh) 4.2 (English)
| - | ||||||||||||||||||
| For additional Year 2000 compliance information please see the individual Office 4.2, Macintosh Edition, application Product Guides. | ||||||||||||||||||
| Macintosh OS | ||||||||||||||||||
| System clock | ||||||||||||||||||
| 19 Mar 1999 | ||||||||||||||||||
|
Operational Range for Data: System dependentPrerequisites:Opening Microsoft PowerPoint 98 files in Microsoft PowerPoint 4.x with the use of post-ship import converters may result in an incorrect date format. To correct this problem, PowerPoint Translator 8-4 version 8.0.2 must be downloaded from the PowerPoint 98 product guide. For additional Year 2000 compliance information please see the individual Office 4.2, Macintosh Edition, application Product Guides.The below information refers to the code that is shared between Office 4.2, Macintosh Edition applications. Please see the individual Office 4.2, Macintosh Edition, application Product Guides for more detailed Year 2000 information on the product. 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 four-digit year dates and displayed according to user settings in the operating system. Setup has no date sensitivity, except with identifying qualified upgrade products. See below for testing implications. Two-digit shortcut handling: See the individual Office 4.2, Macintosh Edition, application Product guides for how each product handles 2-digit shortcuts. Common date usage errors:
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.
| ||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Macintosh) 98 (English)
| - | |||||||||||
| See below | |||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | |||||||||||
| System clock | |||||||||||
| 22 Apr 1999 | |||||||||||
|
Prerequisites: For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). Please review those individual product guides to determine if your organization is likely to require those upgrades.The below information refers to the code that is shared between Office 98 applications. Please see the individual Office 98 applications for more detailed information on the product. Description of how the product handles dates: PP7TRANS.DLL version 8.01 required for correct handling of short dates when saving presentations to Microsoft Power Point 4.0 format. All other components and functionality of Office are compliant and shipped. 2-digit shortcut handling: Systems display options only within the shared office features. See individual applications. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data or, if necessary, plain text data should be saved and manipulated with the full 4-digit year. VBA and ODBC will correctly handle all 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. 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.
| |||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Macintosh) 98 (French)
| - | |||||||||||
| For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). | |||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | |||||||||||
| System Clock | |||||||||||
| 18 Mar 1999 | |||||||||||
|
Prerequisites: For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). Please review those individual product guides to determine if your organization is likely to require those upgrades.The below information refers to the code that is shared between Office 98 applications. Please see the individual Office 98 applications for more detailed information on the product. Description of how the product handles dates: PP7TRANS.DLL version 8.01 required for correct handling of short dates when saving presentations to Microsoft Power Point 4.0 format. All other components and functionality of Office are compliant and shipped. 2-digit shortcut handling: Systems display options only within the shared office features. See individual applications. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data or, if necessary, plain text data should be saved and manipulated with the full 4-digit year. VBA and ODBC will correctly handle all 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. 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.
| |||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Macintosh) 98 (German)
| - | |||||||||||
| For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). | |||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | |||||||||||
| System Clock | |||||||||||
| 18 Mar 1999 | |||||||||||
|
Prerequisites: For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). Please review those individual product guides to determine if your organization is likely to require those upgrades.The below information refers to the code that is shared between Office 98 applications. Please see the individual Office 98 applications for more detailed information on the product. Description of how the product handles dates: PP7TRANS.DLL version 8.01 required for correct handling of short dates when saving presentations to Microsoft Power Point 4.0 format. All other components and functionality of Office are compliant and shipped. 2-digit shortcut handling: Systems display options only within the shared office features. See individual applications. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data or, if necessary, plain text data should be saved and manipulated with the full 4-digit year. VBA and ODBC will correctly handle all 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. 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.
| |||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Macintosh) 98 (Italian)
| - | |||||||||||
| For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). | |||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | |||||||||||
| System Clock | |||||||||||
| 18 Mar 1999 | |||||||||||
|
Prerequisites: For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). Please review those individual product guides to determine if your organization is likely to require those upgrades.The below information refers to the code that is shared between Office 98 applications. Please see the individual Office 98 applications for more detailed information on the product. Description of how the product handles dates: PP7TRANS.DLL version 8.01 required for correct handling of short dates when saving presentations to Microsoft Power Point 4.0 format. All other components and functionality of Office are compliant and shipped. 2-digit shortcut handling: Systems display options only within the shared office features. See individual applications. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data or, if necessary, plain text data should be saved and manipulated with the full 4-digit year. VBA and ODBC will correctly handle all 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. 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.
| |||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Macintosh) 98 (Japanese)
| - | |||||||||||
| See below | |||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | |||||||||||
| System clock | |||||||||||
| 22 Apr 1999 | |||||||||||
|
Prerequisites: For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). Please review those individual product guides to determine if your organization is likely to require those upgrades.The below information refers to the code that is shared between Office 98 applications. Please see the individual Office 98 applications for more detailed information on the product. Description of how the product handles dates: PP7TRANS.DLL version 8.01 required for correct handling of short dates when saving presentations to Microsoft Power Point 4.0 format. All other components and functionality of Office are compliant and shipped. 2-digit shortcut handling: Systems display options only within the shared office features. See individual applications. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data or, if necessary, plain text data should be saved and manipulated with the full 4-digit year. VBA and ODBC will correctly handle all 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. 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.
| |||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Macintosh) 98 (Spanish)
| - | |||||||||||
| For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). | |||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | |||||||||||
| System Clock | |||||||||||
| 18 Mar 1999 | |||||||||||
|
Prerequisites: For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). Please review those individual product guides to determine if your organization is likely to require those upgrades.The below information refers to the code that is shared between Office 98 applications. Please see the individual Office 98 applications for more detailed information on the product. Description of how the product handles dates: PP7TRANS.DLL version 8.01 required for correct handling of short dates when saving presentations to Microsoft Power Point 4.0 format. All other components and functionality of Office are compliant and shipped. 2-digit shortcut handling: Systems display options only within the shared office features. See individual applications. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data or, if necessary, plain text data should be saved and manipulated with the full 4-digit year. VBA and ODBC will correctly handle all 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. 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.
| |||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Macintosh) 98 (Swedish)
| - | |||||||||||
| For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). | |||||||||||
| Apple Macintosh PowerPC Computers with Mac OS 7.5 to 8.1 | |||||||||||
| System Clock | |||||||||||
| 18 Mar 1999 | |||||||||||
|
Prerequisites: For PowerPoint 98 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PowerPoint Translator 8-4 version 8.0.2, must be downloaded. (see PowerPoint 98 product guide for download). Please review those individual product guides to determine if your organization is likely to require those upgrades.The below information refers to the code that is shared between Office 98 applications. Please see the individual Office 98 applications for more detailed information on the product. Description of how the product handles dates: PP7TRANS.DLL version 8.01 required for correct handling of short dates when saving presentations to Microsoft Power Point 4.0 format. All other components and functionality of Office are compliant and shipped. 2-digit shortcut handling: Systems display options only within the shared office features. See individual applications. Common date usage errors: Data exchange between Microsoft Office applications should avoid use of plain text data or, if necessary, plain text data should be saved and manipulated with the full 4-digit year. VBA and ODBC will correctly handle all 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. 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.
| |||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Chinese - Simplified)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 How is this product Not Compliant?: Office 4.x is not compliant because Excel 5 recognizes all 2-digit years as the 20th century. This can be avoided if users enter all 4-digit for the year when referring to a 21st century date. For more detailed information, please see the individual applications product guide. Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides.
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Chinese - Traditional)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Czech)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 04 Mar 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Danish)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Dutch)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (English)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Finnish)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (French)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (German)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Greek)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System Clock | |||||||||||||||||||||
| 03 May 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Hungarian)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System Clock | |||||||||||||||||||||
| 04 Mar 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Italian)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Japanese)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Korean)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 How is this product Not Compliant?: Office 4.x is not compliant because Excel 5 recognizes all 2-digit years as the 20th century. This can be avoided if users enter all 4-digit for the year when referring to a 21st century date. For more detailed information, please see the individual applications product guide. Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides.
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Norwegian)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Spanish)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Swedish)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 26 Jan 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 4.XX (Thai)
| - | |||||||||||||||||||||
| None | |||||||||||||||||||||
| See below | |||||||||||||||||||||
| System clock | |||||||||||||||||||||
| 07 Apr 1999 | |||||||||||||||||||||
|
Operational Range for Data: System dependentRelease Date: October 1993 – October 1994 Product Dependencies: Thai Windows 3.1, or Thai NT 4.0 or greater. Thai Office 4.x includes the English version of PowerPoint 4. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in PowerPoint 4 with the use of post-ship import converters will result in an incorrect date format. For more details see the individual application Product Guides. The below information refers to the code that is shared between Office 4.x documents. Please see the individual applications for more detailed information on the product. Description 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 with identifying qualified upgrade products. Since the dates of these products are handled by the operating system and do not change, year 2000 does not affect this behavior. 2-digit shortcut handling: System display options only within the shared Microsoft Office features. See individual applications. Common date usage errors:
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).
| |||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Arabic)
| - | ||
| PP7TRANS.DLL version 7.07.1060 | ||
| Arabic Windows 95, Arabic Windows 98 | ||
| System clock | ||
| 29 Jul 1999 | ||
|
Operational Range for Data: System dependentPrerequisites: For Microsoft PowerPoint 95 to execute short dates (2-digit year format) in the 2000s when saving to Microsoft PowerPoint 4.0 format, a new version of the translator, PP7TRANS.DLL version 7.07.1060, must be downloaded. Click here to download PP7TRANS.DLL v. 7.07.1060*Note: The below information refers to the code that is shared between Arabic Office 95 documents. Please see the individual applications for more detailed information on the product. How the product handles dates: Dates and times that are displayed or query-able by the user are obtained from the operating system’s 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 setup file removal. See below for testing implications. For Visual Basic for Applications (VBA) and the shared Office object model: Dates and times displayed are obtained from the operating system clock. 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 stored as a 4-digit year value. Since a common programming language (VBA 4.0) is used by the Office applications, date handling for 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 Arabic 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
CreationDate Property LastPrintDate Property LastSaveTime Property PropertyTests Collection- Conditions for PropertyTests may be dates e.g. msoConditionNextMonth Add Method Condition Property FileSearch Object LastModified Property Two-digit shortcut handling:
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.
For VBA and the shared Office object model: In the original configuration, 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 OSR 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.4118 or later to the c:\Windows\System (Windows 95) or c:\WINNT\System32 (Windows NT) directories on the affected computers. This will ensure that the date handling characteristics for 2-digit dates are consistent with the date window approach outlined above. For additional Information please see the VBA Year 2000 Product GuideRecommendations for working with dates:
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 4-digit year. Text values that contain date data should be checked to ensure that they contain the full 4-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 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 issues. 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 side effects with other products cannot be predicted. Interoperability testing across Microsoft Office products can be conducted safely. Setup maintenance mode (for file removal), the only date sensitive portion of Microsoft 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. The above test need to be conducted with System Calendar set to Gregorian and Hijri. 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. Set the system date to the Hijri date 09/24/1420 - equivilant to December 31, 1999, and have it roll over to the year 2000. Revert the Calendar back to Gregorian and make sure the updating mechanism of 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. Set the system date to Hijri. Use the same file above. Perform a search using an Office App for files created after 09/23/1420 – equivalent to December 30, 1999. Make sure 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. Set the System Calendar to Hijri. Create a file last modified on 09/25/1420 - equivalent to January 1, 2000. Perform a search using an Office App for files last modified after 09/23/1420 – equivalent to December 30, 1999. Make sure 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. Switch the system date to Hijri. Create a file last printed on 09/25/1420 Hijri. Perform a search using an Office App for files last modified after 09/23/1420 Hijri. Verify 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 Application for files with that property set to a date later than December 30, 1999 and verify that the file was found. Switch System Calendar to Hijri. Use the same file you created. Perform a search using an Office Application for files with that property set to a date later than 09/23/1420 Hijri. 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. Microsoft recommends performing this on a clean machine with Office version 95 installed and combinations of dates spanning the turn of 1999 to 2000. 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 issues that are outside of the scope of the testing that was done at Microsoft. The date usage issue described above can cause unwanted behavior 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 2-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 (Canadian French)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System Clock | ||
| 16 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/o95y2kinternational.htm.Description 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 (Chinese - Simplified)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 06 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 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.
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/china/downloadDetails/O95y2k.htm
Recommendations:
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:
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
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
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 Guide
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.
Users testing applications written in VBA should be especially careful to test four main problem areas:
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()
End Sub
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Chinese - Traditional)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 23 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 Chinese Traditional by providing software updates for identified issues through January 1, 2001, except for the existing Emperor Dating System issues. Newer Service Packs are also to be maintained at least as Compliant*# with the same Emperor Dating System exception coupled with intent to fix other identified issues, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.An Office 95 Year 2000 software update will be available in June 1999 that will correct known Year 2000 related issues in the applications used in Office 95. For specific issues remediated by this software update see http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htm
Prerequisites: An Office 95 Year 2000 update is now available. For more detailed information and to download this update please go to http://www.microsoft.com/taiwan/download/office.htm.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. Description 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:
Microsoft Office Language Reference
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
End Sub
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Czech)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System clock | ||
| 16 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/o95y2kinternational.htm.Description 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 (Danish)
| - | ||
| 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 (Dutch)
| - | ||
| 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 (English)
| - | ||
| Office 95 Year 2000 Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System Clock | ||
| 19 Jul 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Office 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. 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 download 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:
2) Download the Office 95 Year 2000 update from http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htm3) 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 (Finnish)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System Clock | ||
| 16 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/finland/downloadDetails/O95y2k.htm.Description 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 (French)
| - | ||
| 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 (German)
| - | ||
| 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 (Greek)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System Clock | ||
| 24 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 (Hebrew)
| - | ||
| PP7TRANS.DLL version 7.07.1060 | ||
| Hebrew Windows 95, Hebrew Windows 98 | ||
| System clock | ||
| 29 Jul 1999 | ||
|
Operational Range for Data: System dependentPrerequisites: For Microsoft PowerPoint 95 to execute short dates (2-digit year format) in the 2000s when saving to Microsoft PowerPoint 4.0 format, a new version of the translator, PP7TRANS.DLL version 7.07.1060, must be downloaded. Click here to download PP7TRANS.DLL v. 7.07.1060*Note: The below information refers to the code that is shared between Hebrew Office 95 documents. Please see the individual applications for more detailed information on the product. How the product handles dates: 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 4-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 Visual Basic for Applications (VBA) and the shared Office object model: Dates and times displayed are obtained from the operating system clock. 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 stored as a 4-digit year value. Since a common programming language (VBA 4.0) is used by the Office applications, date handling for 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 Hebrew 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
CreationDate Property LastPrintDate Property LastSaveTime Property PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth Add Method Condition Property FileSearch Object LastModified Property Two-digit shortcut handling:
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.
For VBA and the shared Office object model: In the original configuration, 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 OSR 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 Office 95 applications will use 2-digit date handling logic consistent with the oleaut32.dll version. Users should load oleaut32.dll v2.20.4118 or later to the c:\Windows\System (Windows 95) or c:\WINNT\System32 (Windows NT) directories on the affected computers. This will ensure that the date handling characteristics for 2-digit dates are consistent with the date window approach outlined above. For additional Information please see the VBA Year 2000 Product Guide
Recommendations for working with dates:
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 4-digit year. Text values that contain date data should be checked to ensure that they contain the full 4-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 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 issues. 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 side effects with other products cannot be predicted. Interoperability testing across 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. The above test need to be conducted with System Calendar set to Gregorian and Hebrew Lunar. 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. Set the system date to the Hebrew Lunar date 22 Tevet 5760 - equivalent to December 31, 1999, and have it roll over to the year 2000. Revert the Calendar back to Gregorian and make sure the updating mechanism of 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. Set the system date to Hebrew Lunar. Use the same file above. Perform a search using an Office App for files created after 21 Tevet 5760 – equivalent to December 30, 1999. Make sure 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. Set the System Calendar to Hebrew Lunar. Create a file last modified on 23 Tevet 5760 - equivalent to January 1, 2000. Perform a search using an Office App for files last modified after 21 Tevet 5760 – equivalent to December 30, 1999. Make sure 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. Switch the system date to Hebrew Lunar. Create a file last printed on 23 Tevet 5760. Perform a search using an Office App for files last modified after 21 Tevet, 5760. Verify 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 Application for files with that property set to a date later than December 30, 1999 and verify that the file was found. Switch System Calendar to Hebrew Lunar. Use the same file. Perform a search using an Office Application for files with that property set to a date later than 21 Tevet 5760 Hebrew.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 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. Microsoft recommends performaing this on clean machine and on machine with Office version 95 installed and combinations of dates spanning the turn of 1999 to 2000. 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 issues that are outside of the scope of the testing that was done at Microsoft. The date usage issue described above can cause unwanted behavior 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 2-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 | ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Hungarian)
| - | |||||||||||||||||||||||
| Office 95 Year 2000 Software Update | |||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | |||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||
| 24 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 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.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
| |||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Italian)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System Clock | ||
| 16 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 (Japanese)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System clock | ||
| 20 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 Japanese by providing software updates for identified issues through January 1, 2001, except for the existing Emperor Dating System issues. Newer Service Packs are also to be maintained at least as Compliant*# with the same Emperor Dating System exception coupled with intent to fix other identified issues, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.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://www.microsoft.com/japan/Office/OfficeFreeStuff/Office/O95y2k/.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. Description 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 GuideCommon 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 (Korean)
| - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 or greater | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 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.
Recommendations:
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. Description 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:
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
PropertyTests Collection- Conditions for PropertyTests may be dates eg msoConditionNextMonth
FileSearch Object
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 Guide 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.
Users testing applications written in VBA should be especially careful to test four main problem areas:
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()
End Sub
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Norwegian)
| - | ||||||||||||||||||||
| 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.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.htm.Description of how the product handles dates: Storage. Microsoft Excel stores dates as numeric values, with day #1 being 01/01/1900. Excel 95 recognizes 01-JAN-1900 through 31-DEC-2078 as valid dates. 01/01/2000 is stored as value 36526, since it is the 36526 th day in the century.Formatting. When Microsoft Excel formats a date, it uses one of several default formats. The most common is the system short date. If the system short date is a YY format (refers to a 2-digit year entry), then even when the user types a YYYY (refers to a 4-digit year entry) date, it will by default display in a YY format. The format can be changed. To avoid any ambiguity we recommend changing the system short date to a YYYY format. Parsing on date entry. If a user enters a date in a "M/d/yy" format, less than 20 is 20XX, and equal to or greater than 20 is 19XX. For example, Excel 5 will recognize, "01/01/15" as January 1, 2015, but will recognize "01/01/25" as January 1, 1925. To avoid any possible confusion, users can always display dates in a YYYY format so the century is clearly shown. Leap Year. Microsoft Excel treats 1900 as a leap year for backward compatibility with other products such as Lotus 1-2-3. (See Knowledge Base article Q181370 for more information.)2-digit shortcut handling: What are the acceptable deviations? Common date usage errors: If a date is pasted from one application to another using only the last two digits of the year, Excel might parse the date differently than the originating application calculated it. Example: In a non-Excel application, you have the date January 1, 1915. You copy the date, but your system settings are "M/d/yy", and all that is copied is the text "1/1/15". When you paste "1/1/15" into Excel, it will parse the date to January 1, 2015. Such an error can also occur when one application is using a "M/d/yy" format while another application is using a "d/M/yy" format. This also applies to importing dates from text files. (See KB articles Q180159 for more information.)The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. Recording date entry in a macro only records the year according to the system short date format, which results in parsing a 2-digit year in playback. (See KB article Q180159 for more information.)Using a format such as "Dec 98" will break at the year 2001. This is because 98 is too large to be the day of month, so Microsoft Excel assumes it is a year. However, Microsoft Excel assumes "Dec 01" refers to December 1 of the current year. Since Microsoft Excel always stores the complete date, you can avoid ambiguity by entering a full date regardless of the display formatting. (See KB article Q180952 for more information.)Microsoft Excel handles serial dates, the most common usage of dates, properly. Due to the ambiguous nature of text dates, there is always some potential for error. Use serial dates whenever possible and take great care when transferring text dates. Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should never be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "2/1/25" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025. Defined names store references only as text strings. Since they do not store dates as serial values, they are vulnerable to century issues when a 2Y format is used. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience miscalculations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems. Testing guidelines and recommendations: The following areas should be examined to verify whether dates are being properly used. The table below can be used to guide testing of Excel within your organization.
Additional Testing Instructions Users who work with dates in Microsoft Excel will benefit from changing the system short date format to one that uses a 4-digit year, (i.e. "MM/dd/yyyy"). This change will allow the user to clearly see the century of a date. Conducting the below tests is only worthwhile if 4-digit years are used. If you decide not to set your system short date format to include a 4-digit year, you can format each cell individually by selecting Format/Cells/Number/Custom, and entering a 4-digit year format. To change the system short date format, press the Start button, then select Settings, Control Panel, Regional Settings, select the Date page, then change the Short Date Style to a format that includes a 4-digit year by replacing the "yy" portion with "yyyy". Verify that Microsoft Excel transitions smoothly into the year 2000: Warning! Before conducting this test, make sure you do not have any software containing a license that expires by the year 2000. This is especially common with beta copies of software programs. If a program determines that its license has expired it is possible the program will no longer boot, even after resetting the system clock. Changing a system clock on a network can affect other computers connected to the network, so it is highly recommended that you isolate the computer from all other systems before changing the system clock to conduct the following test. Set the system clock to 11:59 p.m. December 31, 1999. Start Microsoft Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter =NOW(). After one minute, press {F9} to recalculate the formula you entered in A1. Note that the time and date shown will be in the year 2000, and nothing unusual has happened to Excel. Remember to reset your system clock to the correct time and date after conducting this test. Verify that Excel recognizes the year 2000 as a leap year: Start Microsoft Excel. In cell A1 (cell R1C1 if in R1C1 mode), enter "=DATE(2000,2,28)+1". Note that the resulting date is February 29, indicating that Excel correctly recognizes that 2000 is a leap year. Note: The year 1900 is not a leap year. However, in your testing you may notice that Microsoft Excel treats 1900 as a leap year. This algorithm was adopted to maintain compatibility with dates in Lotus 1-2-3, and is by design. The calculation for leap years used by the Gregorian calendar is as follows. If a year is evenly divisible by four, it is a leap year, unless the year is evenly divisible by 100. If a year is evenly divisible by 100, it is not a leap year, unless it is also evenly divisible by 400. (See KB article Q181370 for more information.) | ||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions 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 (Polish)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System clock | ||
| 16 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/poland/downloadDetails/O95y2k.htm..Description 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 (Portuguese (Brazil))
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System Clock | ||
| 18 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/Brasil/downloadDetails/O95y2k.htm.Description 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 (Portuguese)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95 or greater, WIndows 3.51 or greater | ||
| System clock | ||
| 18 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.An Office 95 Year 2000 software update will be available in June 1999 that will correct known Year 2000 related issues in the applications used in Office 95. For specific issues remediated by this software update see http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmOperational 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. Description 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 Guide Recommendations to meet compliance: 1) 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. 2) 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 (Russian)
| - | ||
| Office 95 Year 2000 Software Update | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System clock | ||
| 18 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/rus/downloadDetails/O95y2k.htm.Description 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 (Slovenian)
| - | ||
| PP7TRANS.DLL version 7.07 | ||
| Windows 95, or Windows NT 3.51 or greater | ||
| System clock | ||
| 19 Jul 1999 | ||
|
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Office 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.An Office 95 Year 2000 software update will be available in June 1999 that will correct known Year 2000 related issues in the applications used in Office 95. For specific issues remediated by this software update see http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmOperational 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. Description 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 Guide Recommendations to meet compliance: 1) 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. 2) 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. | |
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.  | ||