Office Professional 97 8.0 (German) - 32-Bit Win
Product Summary
Product: Office Professional 97
Version: 8.0
Category: Compliant*
Operating System: 32-Bit Win
Language: German Release Date: 01 Nov 1996
Operational Range: -
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update; Outlook 97 Year 2000 Software Update
Product Dependencies: 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)
Clock Dependencies: System clock
Last Updated: 01 Jul 1999

Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Office 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://officeupdate.microsoft.com/Articles/sr2fact.htm The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.

Operational Range for Data: System dependent

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.

Area SubArea Testing Recommendations
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      
      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.
      Displayed dates Verify that the displayed dates for the creation/last modified dates of the index show 00 for the year 2000.
     
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      



 

Legend of Symbols:
* Indicates the product is compliant, with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document.
# Indicates the product is compliant, with acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality (ex: data integrity) or stability (ex: reliability) of the product.
+ Indicates the product is compliant, with pending software updates. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

 

Friday, July 9, 1999
1999 Microsoft Corporation. All rights reserved. Terms of use.