The process involves checking, documenting and testing. Checking and documenting hardware, software and applications for dates. These are systems that use dates, but particularly the year represented as '98' rather than '1998'. The lack of a 4 digit year will cause any calculation, sorting, data storage or display of information to be wrong when we begin using the year '2000'. Without correction the systems will at a minimum, be inaccurate, but most likely they will fail.
Testing follows finding and fixing date processing.
Testing is done to make sure that the date problem has been fixed, and also to be sure no new problems have been introduced with the repair. When the testing is successful, we can designate the hardware, software or applications as being Y2K compliant. Over the next several months, I will share with you how our Y2K racing team stretches to beat the year 2000 to the finish line. I also plan to provide you some information about how you can start to check, fix and test you desktop system. You too can join the Y2K team that beats the 2000 deadline.