Editing Dates And Time Source Code For Y 2 K
THIS IS NOT OBSOLETE
| Field | Computer Programs and Databases |
| Went Obsolete | Just after the turn of the Milennium, in January of 2000 |
| Made Obsolete By | Some preparation and absence of any major responses to the new date |
| Knowledge Assumed | The programming language for the source being edited or access to the database being edited |
| When useful | Only if a database or program that relied on the 2 digit method was malfunctioning and needed to be repaired |
The hype about all the potential impending problems arising from the last two digits of the year changing to 00 seemed laughable after New Year's Day 2000. There were a few isolated and minor problems caused, but most major companies prepared well and did the necessary program source and DB editing far ahead of time.No one really knows just what would have happened had precautions not been taken, but the fact is that this skill won't need to be used again for the next century, and maybe never again if full years are used in critical programs and Databases. (Otherwise, there will be the Y10K? problem (http://www3.telus.net/vschmid/essays/9995.htm(approve sites)).)
However, there might be similar problem in 2038 when 32 bit time counters overflow. Precise time is 03:14:07 UTC on Tuesday, January 19, 2038. (wikipedia: http://en.wikipedia.org/wiki/Year_2038_problem).