DEALING WITH DATES - SOLUTIONS FOR THE YEAR-2000

The Y2K problem is real, and it has attracted intense media attention and aggressive vendor response. For whatever reason-whether they wante d to save precious memory ih an era when memory was incredibly expensi ve, or because they didn't expect systems to last this long, or becaus e they simply didn't recognize the problem-programmers long ago adopte d a two-digit convention to represent the year. This convention will c ause failures as we approach the turn of the century and beyond. On Ja nuary 1, 2000, uncorrected software will assume that the maximum value of a year field is 99 and will roll systems over to the date 1900 ins tead of 2000, resulting in negative date calculations. Incorrect leap year calculations will incorrectly assume that the year 2000 has only 365 days instead of 366. What's more, many date-dependent algorithms a nd forward-referencing systems are already beginning to fail. Approach es for resolving the problem and managing the risks have tended to foc us on how particular tools and vendors can help. This article sets for th the concepts, terminology, and individual aspects of a Y2K effort a nd then defines a process that an organization can use to address its own Y2K challenge in a forthright and level-headed manner.