The Year 2000 Problem -- Resources for dealing with the problem and a call for action ... It doesn't take a great imagination to see that a few organizations will experience disruptions due to the Year 2000 problem.
|
www.disastercenter.com/year2000.htm
www.disastercenter.com/year2000.htm
· Cached
|
|
“ |
You will be hearing about the "Year 2000" problem constantly in the news this year. And you will hear a lot of conflicting information in the process. There is also a good bit of "end of the world" rhetoric floating arou...
http://computer.howstuffworks.com/y2k.htm
|
|
According to numerous sources, the Year 2000 Problem (also known as the Millennium Bug) really only exists for large COBOL-based legacy systems. ... This paper is designed to explain the Year 2000 problem as it relates to the following Microsoft desktop products:
|
www.fmsinc.com/tpapers/year2000/index.html
www.fmsinc.com/tpapers/year2000/index.html
· Cached
|
|
What exactly is the Year 2000 problem? Since the early development of computerized business applications, programmers have tended to use a two-digit date scheme to save storage space and reduce the complexity of calculations, yielding better system performance.
|
www.comlinks.com/legal/tmjb1.htm
|
|
|
|
Following a ten-year temporary residence in Philadelphia, the Senate met for the first time in the District of Columbia. Construction of the new capitol had begun in 1793, but materials and labor proved to be more expensive than anticipated.
|
Why Has The Year 2000 Problem Happened? (Michael Gerner). What caused the so-called Millenium Bug? ... Will The Year 2000 Problem Affect Me? ("Doc" Don Taylor) ... Economic Impact of the Year 2000 Problem...
|
www.compinfo.co.uk/y2k.htm
· Cached
|
|
The year 2000 problem could have been completely prevented had some early people envisioned the degree to which the microprocessor would change our lives. Surely, no one would have thought that in the early days of ENIAC that everything from your alarm clock to your car would be computerized.
|
www.deepsky.com/~merovech/millennium.html
|
|
Most software developed in the 1960s, 1970s, and 1980s (and some in the 1990s) was not engineered to be operable in the 21st Century. Why this happened is easy to understand: memory, disk space, and cycle time were scarce - performance was prized more than robustness. ... Top : Y2K: The Year 2000 Problem...
|
www.thedacs.com/databases/url/key.php?keycode=13
|
|
