>I suspect that a higher percentage of those with Y2K problems are operating mainframes with apps built at a time of very expensive disk storage. It is the mgmt of these companies or institutions that has been responsible to accepting the task of Y2K and for those that haven't seen it coming or bothered to recognize it, oh well, they should get fired. For those that are just working at these places, no one should be pointing fingers at programmers and thinking that their jobs are cushy. When the Y2K #*$&% starts rolling down hill, though the current crop of programmers didn't create the mess, it'll be in their hands to fix.
>

True. It is often the bigger businesses that create problems like this. Believe me the #*$&% has already started rolling. In Australia two plants shut down because of a scheduled shut down in 2097 was interpreted as 1997. This cost these two companies a combined total of $700,000,000+. Mom and Pop stores who are refusing to update their credit card readers are reading the 00 expiration as 1900. These are just a couple of examples.