> thanks. just confirms that witango isn't y2k compliant in that a
> 2-digit year will always be force to last century, and coders need to
> be on guard to code in rules to make proper assumptions when a 2-digit
> year comes in.
You are not correct in this statement. None of the tests state that Y2K compliant applications should be able to guess which century the user intended a 2 digit year to fall into.
The tests for Y2K compliance are:
The application has to be able to:
1 Roll over from 1999 to 2000 while running.
2 Retain the correct system date after rebooting.
3 Store and calculate dates consistent with a 4-digit format throughout its operational range
4 Recognise the year consistently where a 2-digit short cut for the year is entered
5 Perform date calculation in seconds and the actual date returned correctly executes leap year calculations providing the fact that the OS, firmware and hardware correctly understand a leap year
6 Operate with dates into the 21st century through the end of year 2035
Phil
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
