tag:blogger.com,1999:blog-497787815177352569.post7928812169660628529..comments2024-01-03T08:55:04.827-05:00Comments on SQL Anywhere: Great Moments In History: Y2KBreck Carterhttp://www.blogger.com/profile/15975598564711761434noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-497787815177352569.post-87100649286655326252008-02-26T12:40:00.000-05:002008-02-26T12:40:00.000-05:00The real question is: was Y2K a non-issue, or did ...The real question is: was Y2K a non-issue, or did all the significant Y2K problems get fixed in time so that it <I>looked</I> like a non-issue?<BR/><BR/>My wife worked for a steel company, and they did a Y2K test in the mid-90's by setting all their clocks to 11:55pm Dec 31 1999. At midnight, the whole plant shut down. It turned out to be an exhaust fan deep in the bowels of the plant which decided that it hadn't had scheduled maintenance in 100 years, so it shut down. Everything that depended on it also shut down, and so on. By the time the real 1/1/2000 came around, this and other problems had been fixed and the plant kept right on ticking.<BR/><BR/>There's no way to really know how many problems <I>would</I> have happened had people not been diligent in the 90's. Having said that, you're probably right that a lot more time was spent fixing stuff than was actually necessary.Graemehttps://www.blogger.com/profile/17631487565943415701noreply@blogger.com