General Integrity
No value for current date will cause any interruption in operation.
1. Does ArcInfo, including its extensions, run successfully on the following high-risk dates?
September 9, 1999
December 31, 1999
January 1, 2000
February 29, 2000
2. Does ArcInfo continue to run successfully after the system date rolls over on high-risk dates?
December 31, 1998-January 1, 1999
September 9, 1999-September 10, 1999
December 31, 1999-January 1, 2000
February 29, 2000-March 1, 2000
3. Does the License Manager continue to run on the following high-risk dates?
January 1, 2000
January 2, 2000
Date Integrity
Date-based functionality must behave consistently for dates prior to, during, and after the Year 2000.
1. What is the valid date range for ArcInfo date data type?
2. Does ArcInfo return the correct value for DATE for the high-risk dates (see list above)?
3. Does ArcInfo return the correct value for DATE after the system date rolls over on high-risk dates?
4. Does INFO correctly handle data arithmetic across the centuries?
5. Does the License Manager report correct date information during and after the Year 2000?
Explicit/Implicit Century
In all interfaces and data storage, the century in any date must be specified explicitly or by unambiguous algorithms or inferencing rules.
1. Does ArcInfo date data type permit setting explicit values for century?
2. Does ArcInfo allow two-digit century? What are the inference rules for two-digit century?
Leap Year
Year 2000 must be recognized as a leap year.
Is February 29, 2000, a valid date in ArcInfo?
