Reply to post: Why

Y2K quick-fix crick? 1920s come roaring back after mystery blip at UK's vehicle licensing agency

HildyJ Silver badge


Being old enough to have gone through Y2K with mainframe COBOL systems, the problem was not that people didn't have the time or money to fix the software, it was that the databases fixes were orders of magnitude more difficult than software fixes. Some sacrificial lamb had to go to the CEO and tell him he needed to shut down all processing for an indeterminate length of time (definitely more than overnight) while all the database records were rewritten to insert "19" in all the date fields. It was not an easy sell for companies with millions of records.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon


Biting the hand that feeds IT © 1998–2020