Laserfiche WebLink
Enclosure 4 <br /> Potential Problematic Dates <br /> Date Potential Problems <br /> 01/01/1999 -Systems that look one year ahead may fail. <br /> 04/09/1999 - Special-use Julian date(99th day or 99th year). <br /> 07/01/1999 - Many governments begin their fiscal year. <br /> 08/21/1999 -Global Positioning System date rollover affects <br /> military, transportation, Geographic Information <br /> System,and Automatic Vehicle Locator. <br /> 09/09/1999 -Programmers use 9/9/99 as file purge date or infinity; will <br /> cause numerous problems (ninth day of ninth month of <br /> ninety-ninth year) <br /> 10/01/1999 - Federal government and others begin FY 2000. <br /> 12/31/1999 -End-of-year baseline (to be used in rollover scenario). <br /> 01/01/2000 - Date rollover will halt, confuse,or otherwise disrupt many <br /> systems and devices. <br /> 01/02/2000 -First 24-hour look back period. <br /> 01/10/2000 -First date requiring full use of seven digits. <br /> 02/28/2000 -Day prior to Leap Year(to be used in rollover scenarios). <br /> 02/29/2000 - Many systems will not recognize Leap Year in 2000. <br /> 02/30/2000 -Invalid date. Test to ensure that Leap Year logic is <br /> functioning. <br /> 03/01/2000 -First valid date after Leap Year. <br /> 10/10/2000 -First date requiring full use of eight digits; may cause <br /> failures. <br /> 12/31/2000 - Some systems using Julian dates may not recognize the 366th <br /> day of the Leap Year. <br /> 01/01/2001 -First date in 2001 (to be used in rollover scenarios). <br /> Sources: Texas Guidebook 2000 and California Year 2000 Embedded Systems <br /> Program Guide. <br /> E4-1 <br />