Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Word (Macintosh) 6.XX (Danish) - Mac
Product Summary |
Product: Word (Macintosh) Version: 6.XX |
Category: Compliant# Operating System: Mac |
Language: Danish |
Release Date: 01 Aug 1994 |
Operational Range: |
01 Jan 1904 - 31 Dec 2035 |
Prerequisites: |
None |
Product Dependencies: |
Macintosh Operating System |
Clock Dependencies: |
System Clock |
Last Updated: |
06 Aug 1999 | |
Product Details |
How the product handles dates:
- Storage. Date and time values for all date usage in Word are stored either as simple text strings or as a 32 bit integer (date is represented by a 4-digit year). If the date information is stored in a 32 bit integer, the data is represented by bit fields that have the following ranges:
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, all features within Word that manipulate dates store the dates as a 32-bit integer. This convention means that the date is represented by a 4-digit year, eliminating the risk of date errors. For example, dates saved within Word documents are stored as 4-digit years, regardless of how they are displayed to the user. Similarly, all revision marking date information retains the 4-digit year designations.
- 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.
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.
- Saving to an earlier version of Word, or upgrading, will have no affect on dates within a document. All 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 Word fields) assumes a date window of 1901 through 2000.
What are the acceptable deviations?
All 2-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 behavior is exposed in table date sorting, quote fields, text form field date formatting, custom document properties, WordBasic date text to date conversions, and Find File Advanced Search. It is not exposed by more common uses of the product such as: inserting a date from the menu, by date fields, or by any other date functionality in Word.
All dates that are used in the Find File Advanced Search dialog time stamp tab are converted to 2-digit format. The year 00 is interpreted as the year 2000. All other years are assumed to be in the 20th century. This means that the operational range of dates for Find File in Word 6.0x for Mac is 1901û2000. The current system date and/or the current system date formatting have no effect on this functionality of Find File. Other than the above mentioned scenario, there are no other negative consequences for typical use of the Find File functionality in Word.
Recommendations:
- Because of the way that 2-digit shortcuts are handled in Word 6.x, users should enter 4-digit years for their dates.
- The one feature where the user is not able to use 4-digit years is in the advanced functionality of Find File. For users running Find File, they can use the file search feature that is provided with the operating system, or a third party search utility.
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 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 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 examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Word within your organization.
Area |
SubArea |
Testing Notes |
Edit |
Insert Date/Time
Table Sort |
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 is interpreted as the year 2000, all other two digit years are interpreted as being in the 20th century. Table Sort recognizes the years 1900 through 2035. |
File |
File Native
RTF
Text Conversions
Graphics Filters
Document Properties
Revision Marking
Find File |
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. |
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, EditTime, Info whose types include CreateDate, EditTime, PrintDate, and SaveDate, PrintDate, SaveDate, and Time.
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. |
Mail |
Doc Routing
Posting
Mail Merge
SendMail |
|
Macros |
WordBasic |
The WordBasic commands that manipulate date and time information are:
AppInfo$(21-26)
Date$()
DateSerial()
DateValue()
Day()
Days360()
DocumentStatistics .Created, .LastSaved, .Printed, .Time
Hour()
InsertDateField
InsertDateTime
InsertTimeField
Minute()
Month()
Now()
OnTime
Second()
Time$()
TimeSerial()
TimeValue()
Today()
ToolsRevisionDate()
ToolsRevisionDate$()
Weekday()
Year() |
Misc. |
Boot / Exit
OLE (Links)
DDE
Environment |
|
Print |
Summary Information |
The last date that the document was printed is saved with the document. |
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. |
Wizards |
Calendar Wizard |
A range of dates can be selected to use with the Calendar Wizard. |
| |
Return to Search Screen
Legend of Symbols: |
* |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
# |
The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
+ |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
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://www.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.
|