Product Entry Guide Detail
------------------------
Microsoft Year 2000 Resource Center
Word 95 7.0 (Arabic)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||
| Arabic Windows 95 localized and enabled versions. | ||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||
| 05 Aug 1999 | ||||||||||||||||||||||||||||||||
|
How the product handles dates:
Hours: 0-23 Minutes : 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32-bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields.
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
| ||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Word 95 7.0 (Chinese - Simplified)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||
| 02 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 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/china/downloadDetails/sr2off97.htm.How the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32-bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. Table/Sort does not interpret Double Byte dates strings as date values. They are interpreted as plain text. Single byte dates are interpreted as described above. Table/Sort does not interpret single byte "00" year strings as date values when entered in YMD date order. This will be corrected with the Year 2000 patch that will be accessible from this site shortly.
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendation: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
| ||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Word 95 7.0 (Chinese - Traditional)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| 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 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. For more detailed information and to download this update please go to http://www.microsoft.com/taiwan/download/office.htm.How the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32-bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. Table/Sort does not interpret Double Byte dates strings as date values. They are interpreted as plain text. Single byte dates are interpreted as described above. Table/Sort does not interpret single byte "00" year strings as date values when entered in YMD date order. This will be corrected with the Year 2000 patch that will be accessible from this site shortly.
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
| ||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Word 95 7.0 (Hebrew)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||
| Hebrew Windows 95/98 in both enabled and localized versions | ||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||
| 05 Aug 1999 | ||||||||||||||||||||||||||||||||||||||
|
How the product handles dates:
Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. Common date usage errors: In general, the entry, importing or formatting of years as 2-digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier documentation, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
| ||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Word 95 7.0 (Japanese)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | |||||||||||||||||||||||||||||||||||
| Windows 95 or Windows NT 3.51 | |||||||||||||||||||||||||||||||||||
| 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 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. For more detailed information and to download this update please go to http://www.microsoft.com/japan/Office/OfficeFreeStuff/Office/O95y2k/.How the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32-bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. Table/Sort does not interpret Double Byte dates strings as date values. They are interpreted as plain text. Single byte dates are interpreted as described above. Table/Sort does not interpret single byte "00" year strings as date values when entered in YMD date order. This will be corrected with the Year 2000 patch that will be accessible from this site shortly.
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. In the Japanese version, Emperor dates are designated with digits 1-xxx. Dates will be sorted through this range and are not concerned with year 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
| |||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Word 95 7.0 (Portuguese (Brazil))
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||
| 05 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.htmHow the product handles dates:
Hours: 0-23 Minutes : 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32-bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields.
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
| ||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Word 95 7.0 (Thai)
| 01 Jan 1901 - 31 Dec 2035 | |||
| None | |||
| Thai Windows 95 | |||
| System clock | |||
| 12 Nov 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
Word 95 7.XX (Canadian French)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||
| 21 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 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/o95y2kinternational.htm.Description of how the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Czech)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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/o95y2kinternational.htm.Description of how the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Danish)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Dutch)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (English)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Update | ||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||
| 21 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 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.htmHow the product handles dates:
Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. Common date usage errors: In general, the entry, importing or formatting of years as 2-digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier documentation, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (English British)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Update | ||||||||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||
| 21 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 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.How the product handles dates:
Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. In Japanese, Emperor dates are designated with digits 1-xxx. Dates will be sorted through this range and are not concerned with year 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier documentation, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Finnish)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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/finland/downloadDetails/O95y2k.htm.Description of how the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (French)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (German)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Greek)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Hungarian)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Italian)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Korean)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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.htmHow the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32-bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. Table/Sort does not interpret Double Byte dates strings as date values. They are interpreted as plain text. Single byte dates are interpreted as described above. Table/Sort does not interpret single byte "00" year strings as date values when entered in YMD date order. This will be corrected with the Year 2000 patch that will be accessible from this site shortly.
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Norwegian)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Polish)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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/poland/downloadDetails/O95y2k.htm.Description of how the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Portuguese)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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/Portugal/downloadDetails/O95y2k.htm.Description of how the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Russian)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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/rus/downloadDetails/O95y2k.htm.Description of how the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Slovenian)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| none | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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.htmDescription of how the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Spanish)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Swedish)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 95 7.XX (Turkish)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||
| Office 95 Year 2000 Software Update | ||||||||||||||||||||||||||||||||
| Windows 95, or Windows NT 3.51 | ||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||
| 21 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 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/Turkiye/downloadDetails/O95y2k.htm.Description of how the product handles dates:
Hours: 0-23 Minutes: 0-59 Seconds: 0-59 Weekday: 0(Sun)-6(Sat) Day of Mo.: 1-31 Year: 1900-2411 Unless otherwise noted, all features within Microsoft Word that manipulate dates store the dates as a 32 bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, all revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this instance, text strings can be interpreted as date values. The two-digit year ’00 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. If the user wants to sort dates in the 21st century, they should use the full four digits. There is no validation of the dates in Table/Sort, so, for instance, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900 through 2035. The same 1901-2000 window is used for interpretation of two digit dates when using Date formatting (picture switch) of Quote Fields. 2-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Word fields) assumes a date window of 1901 through 2000. What are the issues? All two digit shortcuts for dates are assumed to be in the 20th century with the exception of 00, which is interpreted as the year 2000. Note: This functionality is exposed only in the Word Basic macro language, quote fields, date formatted text form fields and in table sort. It is not exposed by the more typical uses of dates, including Insert Date, Insert Field (Date and Time), or file attributes. Recommendations: Because of the way that 2-digit shortcuts are handled in Microsoft Word 95, users should enter 4-digit years for their dates.
Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier, suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. 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 with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Word 95, 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 95 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
Word 97 8.0 (Arabic)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Arabic Windows 95 Localized and Enabled versions, Arabic Windows 98 Localized and Enabled versions, or Arabic Windows NT 4.0 (no SP required) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||
For all Arabic Office 97 applications and with the exception of Outlook 97, if the user enters a date that uses a two-digit year in the Custom tab of the Properties dialog box, the date will be formatted with a value between 1900 - 1999. As an example the user does the following: Selects Properties or Database Properties from the File menu. Clicks the Custom tab. Enters a field name in the Name edit box. Selects date from the Type list. Enters the value 7/5/00 in the value field. Clicks Add. 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.Storage . Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
Word 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 Word 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
Word 97 8.0 (Canadian French)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Chinese - Simplified)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
How the product handles dates: Storage. Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Microsoft Word fields) assumes a date window of 1930 through 2029. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier documentation suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 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 Word 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
Word 97 8.0 (Chinese - Traditional)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
How the product handles dates: Storage. Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Microsoft Word fields) assumes a date window of 1930 through 2029. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier documentation suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 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 Word 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
Word 97 8.0 (Czech)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Danish)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Dutch)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (English)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
In general, avoid testing in a production environment because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely.
The following areas should be looked at to verify that dates are being properly used. The following table can be used to guide testing of Word within your organization.
Word 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 Word 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
Word 97 8.0 (English)
| 01 Jan 1901 - 31 Dec 2035 | ||
| Windows NT 4.0 (no SP required) | ||
| System clock | ||
| 22 Sep 1999 | ||
|
Note: The Office 97 Service Patch 2 is currently not available for English Word 97 for Alpha.
Hours: 0-23
Minutes: 0-59
Seconds: 0-59
Weekday: 0(Sun)-6(Sat)
Day of Month: 1-31
Year: 1900-2411
Unless otherwise noted, features within Microsoft Word that manipulate dates store the dates as a 32-bit integer. What this means is dates saved with versions of documents retain their 4-digit year designations, regardless of display. Similarly, revision marking date information retains the 4-digit year designations.
The one exception is with the Table/Sort command. In this command, text strings can be interpreted as date values. Two-digit years from 00 to 29 are assumed to be in the years 2000–2029. To change this behavior, users should correct 2-digit years to 4-digit years. There is no validation of the dates in Table/Sort. For example, a date of 2/30/2000 would be sorted before 3/1/2000. Table/Sort interprets the range of years 1900–2035. A date window of 1930-2029 is used for interpretation of 2-digit year dates when using Date formatting (picture switch) of Quote Fields. Saving to an earlier version of Microsoft Word, or upgrading, will not have an affect on dates within a document. Date field information and file properties will be retained and recognized. Two-digit shortcut handling: Area SubArea Testing Notes
Edit Insert Date/Time Table Sort AutoComplete Insert Date and Time can insert the current date as text formatted as a date, or as a date field that can be updated. Table Sort can interpret text strings as a date, and sort in chronological order, ascending or descending. Two digits can be interpreted as years. 00 through 29 are interpreted to be 2000 through 2029. Table Sort recognizes the years 1900 through 2035. AutoComplete has a trigger for the current date.
File File Native RTF Text Conversions Graphics Filters Versions Document Properties Revision Marking Date information is stored in the document for creation date, revision date, and the date the document was last printed. Dates are written to RTF in a four-digit format. Date information is stored with text that is marked for revisions. The date information appears in a ToolTip next to the revised text. When multiple versions of a document are saved, date information is saved with each version. This date information can be viewed in the Versions dialog.
Fields Date/Time Fields; Formula Fields; Summary Information Fields; Text Form Fields; Field Picture Switches Many fields exist that manipulate date and time information. CreateDate, Date, DocProperty whose properties include CreateTime, LastPrinted, LastSavedTime, and Total Editing Time, EditTime, Info whose types include CreateDate, EditTime, PrintDate, and SaveDate, PrintDate, SaveDate, and Time. In German, the fields DocProperty: Total Editing Time, EditTime and Info: Edit Time are not available. Quote fields and Text Form fields are text fields that can be formatted as dates using field picture switches. Formula fields are designed to calculate text or numbers.
Macros VBA WordBasic The Visual Basic for Applications methods and properties that manipulate date and time information are: Application.OnTime Conversion.CDate Conversion.CVDate DateTime DateTime.Calendar DateTime.Date DateTime.Date$ DateTime.DateAdd DateTime.DateDiff DateTime.DatePart DateTime.DateSerial DateTime.DateValue DateTime.Day DateTime.Hour DateTime.Minute DateTime.Month DateTime.Now DateTime.Second DateTime.Time DateTime.Time$ DateTime.Timer DateTime.TimeSerial DateTime.TimeValue DateTime.WeekDay DateTime.Year FileSystem.FileDateTime Information.IsDate LetterContent.DateFormat Mailer.SendDateTime Range.InsertDateTime Revision.Date Selection.InsertDateTime VbVarType.vbDate Version.Date WdBuiltInProperty.wdPropertyTimeCreated WdBuiltInProperty.wdPropertyTimeLastPrinted WdBuiltInProperty.wdPropertyTimeLastSaved WdBuiltInStyle.wdStyleDate WdFieldType.wdFieldCreateDate WdFieldType.wdFieldDate WdFieldType.wdFieldEditTime WdFieldType.wdFieldPrintDate WdFieldType.wdFieldSaveDate WdFieldType.wdFieldTime WdSortFieldType.wdSortFieldDate WdTextFormFieldType.wdCurrentDateText WdTextFormFieldType.wdCurrentTimeText WdTextFormFieldType.wdDateText WdWordDialog.wdDialogInsertDateTime The WordBasic commands that manipulate date and time information are: AppInfo$(21-26) Date$() DateSerial() DateValue() Day() Days360() DocumentStatistics .Created, .LastSaved, .Printed, .Time GetDocumentProperty$ CreateTime, LastSavedTime, LastPrinted Hour() InsertDateField InsertDateTime InsertTimeField Minute() Month() Now() OnTime Second() Time$() TimeSerial() TimeValue() Today() ToolsRevisionDate() ToolsRevisionDate$() Weekday() Year()
Doc Routing Mail Merge Outlook Journal Posting SendMail WordMail Mail messages can be sent from within Word. Date and Time functionality that is available with Word is also available within WordMail.
Internal Boot/Quit DDE Environment OLE No applicable notes.
Document Property The last date that the document was printed is saved with the document.
Templates Templates In templates, a combination of two-digit and four-digit years are inserted, and can be modified if necessary.
View Header/Footer Footnotes/Endnotes Comments Status Bar The CreateDate, Date, and PrintDate fields can be inserted into a document's header or footer via the Header and Footer toolbar. These fields are identical to the fields inserted via the Field dialog. The current date is displayed on the word status bar on NT 3.51.
Wizards Calendar Wizard Letter Wizard Fax Wizard A range of dates can be selected to use with the Calendar Wizard. The Letter Wizard can insert a date into a document. The inserted date is a text string, formatted as a date. The Fax Wizard inserts a date into a document. The inserted date can be a 2-digit or 4-digit year.
Word 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 Word 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
Word 97 8.0 (English British)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Finnish)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (French)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (German)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Greek)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Hebrew)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Hebrew Windows 95 Localized and Enabled versions, Hebrew Windows 98 Localized and Enabled versions, or Hebrew Windows NT 4.0 (no SP required) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||
How the product handles dates: 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: Selects Properties or Database Properties from the File menu. Clicks the Custom tab. Enters a field name in the Name edit box. Selects date from the Type list. Enters the value 7/5/00 in the value field. Clicks Add. 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.Storage . Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
String date parsing . Other date values, such as might be imported from another program or entered with an Insert Date/Time command, are simple text. Therefore, they are not handled as date values.
Saving to an earlier version of Microsoft Word, or upgrading, will not have an affect on dates within a document. Date field information and file properties will be retained and correctly recognized. Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Microsoft Word fields) assumes a date window of 1930 through 2029. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier documentation suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 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 Word 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
Word 97 8.0 (Hungarian)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| system clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Italian)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Japanese)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 or the year 2000 software update in Office 97 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
How the product handles dates: Storage. Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Word 97 8.0 (Korean)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
How the product handles dates: Storage. Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Microsoft Word fields) assumes a date window of 1930 through 2029. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier documentation suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 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 Word 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
Word 97 8.0 (Latin America)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Norwegian)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Polish)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Portuguese (Brazil))
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Portuguese)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Download the Office 97 SR2 Patch | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Russian)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Slovak)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||
Storage. Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
Two-digit shortcut handling: Conversion of 2-digit shortcut dates (primarily in table sort and in Microsoft Word fields) assumes a date window of 1930 through 2029. Common date usage errors: In general, the entry, importing or formatting of years as 2 digits should be discouraged or eliminated where date calculation dependencies in the user solutions exist. Since most document content, including data entered through Insert Date/Time and Text Form Fields, is stored as plain text, the century information could be improperly derived or assumed by the user solution. Use of Microsoft Word date field types and pre-defined document and file properties for document-related date calculations will ensure that the available information represents a true date. Because Microsoft Word date fields do not support date arithmetic, we have, in earlier documentation suggested the use of nested formula fields (expressions) to accomplish adding or subtracting days, months, or years to dates. Because simple arithmetic calculations are not calendar-aware, this method is prone to Year 2000-type errors, particularly with 2-digit year values, and is no longer recommended. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Word 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 Word 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
Word 97 8.0 (Slovenian)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Spanish)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Swedish)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Thai)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Thai Windows 95, Thai Windows 98 and Thai Windows NT 4.0 (no specific SP required) | ||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Storage. Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
Word 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 Word 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
Word 97 8.0 (Turkish)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Office 97 Service Release 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 98, Windows 95, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 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.
Word 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 Word 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
Word 97 8.0 (Vietnamese)
| 01 Jan 1901 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Vietnamese Windows 95 | ||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
How the product handles dates: Storage. Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
Word 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 Word 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
Word 98 (Japanese)
| 01 Jan 1901 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Download the Office 97 SR-2 Patch or the year 2000 software update in Office 97 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (SP3 or greater is required, though SP 4 is recommended) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 09 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 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.
How the product handles dates: Storage. Date and time values for date usage in Microsoft Word are stored either as simple text strings or as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. If the date information is stored in a 32-bit integer, the data is represented by bit fields that have the following ranges:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Danish)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Dutch)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (English Australian)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (English British)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (English)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Finnish)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (French)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (German)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Italian)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Latin America)
| 01 Jan 1904 - 06 Feb 2040 | |||||||||||||||||||||||||||||||||||||||||||
| None | |||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | |||||||||||||||||||||||||||||||||||||||||||
| System Clock | |||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | |||||||||||||||||||||||||||||||||||||||||||
|
How the product handles dates:
Two-digit shortcut handling: See 2-digit parsing table above.
Common date usage errors:
| |||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Norwegian)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Portuguese (Brazil))
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Portuguese)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Spanish)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works (Mac) 4.0 (Swedish)
| 01 Jan 1904 - 06 Feb 2040 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Macintosh Operating System | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 03 May 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Summary: The way that Microsoft Works 4.0 for the Macintosh interprets dates that are entered with a 2-digit year value is dependent on the current date setting for the operating system and is summarized in the table below. This product was designed to store dates as serialized numbers, regardless of the visual cell format chosen by the user. Users do not have to go back into files/records and change dates to 4-year format. How the product handles dates: Storage: Microsoft Works 4.0 for the Macintosh stores dates internally as serial numbers from 0 to 49710, where 0 is the serial number for January 1, 1904 and 49710 is the serial number for February 6, 2040. For example, if the date 1/1/1905 is entered, Microsoft Works stores it internally with a value of 366 since this is the number of days since (and including) the serial starting point of January 1, 1904. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 34485 and so on, since this is the number of days since the starting point of 1/1/1904. In addition, Microsoft Works stores 4-digit years in files even when entry uses only 2 digits. Two-Digit Shortcut Handling: If a date is entered with a 2-digit year (i.e. 6/1/98), Microsoft Works 4.0 for the Macintosh has four distinct behaviors, depending on four distinct system date ranges. The table below describes how Microsoft Works 4.0 for the Macintosh interprets a 2-digit year value depending on the current system date (which is set in the operating system):
Sorting: Microsoft Works 4.0 sorts on full years (4-digit dates) even if only 2 digits are displayed. Also, Microsoft Works 4.0 sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Microsoft Works 4.0 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after. Display: Users can select several different visual formats for dates, without changing the underlying value of the actual date itself. The formula bar in the Spreadsheet will display a 4-digit year (YYYY) regardless of the cell format (YY or YYYY). The formula bar in the Database will display the year as 2 or 4 digits, mirroring the default system date format. Additional Information: The DATE() function (which can be used to build formulas in the spreadsheet and database) is not designed to take 2-digit year shortcuts, since it receives numeric parameters. For the Year argument of the DATE() function, numbers less than 1900 are calculated as an offset from 1900. Year arguments with a value of 1900 or greater are interpreted as the 4-digit year value they represent. So, if you were to enter a formula such as =DATE(15,1,1), the resulting date would be January 1, 1915, not 2015. If you were to enter a formula such as =DATE(115,1,1), the resulting date would be January 1, 2015. Similarly, if you were to enter a formula such as =DATE(2015, 1, 1) the resulting date would be January 1, 2015.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Canadian French)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Chinese - Simplified)
| - | ||
| NONE | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Chinese - Traditional)
| - | ||
| NONE | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Czech)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Danish)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Dutch)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (English)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 01 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (English Australian)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 01 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (English British)
| - | ||
| NONE | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Finnish)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (French)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (German)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Hungarian)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Italian)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Japanese)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Norwegian)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Polish)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Portuguese)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Russian)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Spanish)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Swedish)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 2000 5.0 (Turkish)
| - | ||
| None | ||
| Windows 95, Windows 98, Windows 2000, or Windows NT 4.0 Internet Explorer 5, VBRun300.dll (see below) | ||
| System Clock | ||
| 24 Sep 1999 | ||
|
Operational Range for Data: 1/1/1900 through 6/3/2079 for Microsoft Works Spreadsheet and Microsoft Works Database 1/1/1900 through 12/31/2099 for Microsoft Works Calendar and Microsoft Works Word Processor How the product handles dates: Microsoft Works 2000 stores dates in a serialized fashion starting with January 1, 1900 as serial value 1. For example, if the date 1/1/1901 is entered, Works 2000 stores it internally with a value of 367 since this is the number of days since (and including) the serial starting point of January 1, 1900. If the date 6/1/1998 is entered, Microsoft Works stores it internally with a value of 35947 and so on, since this is the number of days since the starting point of 1/1/1900. In addition, Works 2000 stores 4-digit years in files even when entry uses only 2 digits. Parsing on date entry: Works 2000 assumes a date entered with a 2-digit year between 30 and 99 (i.e. 6/1/99), ranges from1930-1999. If the 2-digit-year value is between 00 and 29, Works 2000 assumes the year is 2000 to 2029. In addition, Works Calendar takes advantage of the Regional Settings Properties under the Date Tab in Control Panel in Windows 98 and Windows 2000, by reacting to the "Ending Date" which can be changed to suit the User. By changing this date the entire range of 19xx and 20xx varies accordingly. This means that the century value for a 2-digit year entry can change from the rules described above if the user changes these settings in the Windows 98 or Windows 2000 Regional Settings control panel. Sorting: Works 2000 sorts on full years (4-digit year dates) even if only 2 digits years are displayed. Works 2000 also sorts dates when some are prior to 2000 and some are after 2000. Leap Years: Works 2000 executes leap years and displays 2/29 in appropriate years, including the year 2000 and after though the operational range of the product. Note: The year 1900 is not a leap year. However, Microsoft Works 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. Display: The Works 2000 spreadsheet and database uses the concept of an edit format for dates. This is a short date format with a 4-digit year (i.e. mm/dd/yyyy) and is displayed when a date-formatted cell is selected or edited. For example, when a user navigates the spreadsheet and is currently on a cell with a date format that only displays 2 digits for the year value, the formula bar will display the date in the edit format, which includes 4 digits for the year. If the user places the cell into edit mode, the date is displayed in the edit format as well. This removes the century ambiguity of a 2-digit year component. The Works 2000 word processor can insert the current date as text formatted as a date or as a date field that can be updated. Word processor parses the system time to the display format selected by the user. Two-digit shortcut handling: If the 2-digit year value of a date falls between 30 and 99, that date is interpreted by Works as occurring in 19xx (i.e. between 1930 and 1999). If between 00 and 29 (or in the case of the Calendar, the value set in Control Panel: Regional Settings: Date Tab on Windows 98 or Windows 2000) the two-digit year date is interpreted by Works as occurring in 20xx. What issues are there? Although VBRun300.dll is known to have year 2000 issues, applications that adhere to the Microsoft Year 2000 Compliance Statement can be built with this tool. (See the Visual Basic 3.0 compliance document for details.) Microsoft Works installs VBRun300.dll in the Works directory and other products will not use it from there. Since Microsoft Works does not use the date functionality of VBRun300.dll, the year 2000 compliance of Works is not affected by using VBRun300.dll.
Common date usage errors:
| ||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 3.0 (Canadian French)
| 01 Jan 1900 - 03 Jun 2079 | ||||||
| None | ||||||
| DOS and Windows 3.1 | ||||||
| System clock | ||||||
| 22 Sep 1999 | ||||||
|
Recommendations: Microsoft recommends using 4-digit year entry in cells. No fix will be delivered for Works 3.0 or earlier. Description of how the product handles dates:
2-digit shortcut handling: Works handles all short date years as 19xx. That is, since all dates are converted and stored as a serial value representing the number of days since 1/1/1900, the visual formatting applied to the date has no affect on the actual value of the date itself. However, when initially entering data, if only 2 digits are entered for the year value, Works assumes that the year is 19xx. To enter a date that occurs in the year 2000 or beyond, the date must be entered with its 4-digit year value and the visual formatting changed as desired. Common date usage errors:
| ||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly. | |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. | |
Microsoft Year 2000 Resource Center
Works 3.0 (Chinese - Simplified)
| 01 Jan 1900 - 03 Jun 2079 | ||||||
| None | ||||||
| DOS and Windows 3.1 | ||||||
| System clock | ||||||
| 22 Sep 1999 | ||||||
|
Recommendations: Microsoft recommends using 4-digit year entry in cells. No fix will be delivered for Works 3.0 or earlier. Description of how the product handles dates:
2-digit shortcut handling: Works handles all short date years as 19xx. That is, since all dates are converted and stored as a serial value representing the number of days since 1/1/1900, the visual formatting applied to the date has no affect on the actual value of the date itself. However, when initially entering data, if only 2 digits are entered for the year value, Works assumes that the year is 19xx. To enter a date that occurs in the year 2000 or beyond, the date must be entered with its 4-digit year value and the visual formatting changed as desired. Common date usage errors:
| ||||||
| The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology. | |
| The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product. | |
| The product is compliant . Software updates 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.  | ||