It appears that the Year 2000 may pose a significant problem for these software applications as well as the computers on which they operate. This is one case where an ounce of prevention is worth more than a pound of cure. This is due to the fact that most computers were programmed to identify the year by the last two digits only. When a computer s internal clock tries to roll over to the Year 2000, it may mistakenly believe it's the year 1900 instead of 2000. The following briefly summarizes what can be done to minimize risk from the Y2K problem.
More detail is provided in the complete report.
Assign a project manager or coordinator for all Year 2000 investigations and fixes. An education and awareness program is essential to ensure that staff understands the risks that Year 2000 presents. The impact of problems caused by Year 2000 may range from trivial to extreme. Effort should be concentrated initially on those systems posing the greatest business risk. Determine what systems are and are not Year 2000 compliant.