Re: Year 2000 problem

In <4kkavj$dr0_at_dfw-ixnews3.ix.netcom.com>, usha_at_netcom.ca(Neelesh Anil Shah) writes:

>Can anybody give a clear description about the Year 2000 problem and
>possible solutions for that.

Problem: some software assumes all dates are of the form 19xx; some software that does not make that assumption actually supports dates in other centuries incorrectly.

This problem will obviously affect everyone greatly after midnight, December 31, 1999, but there are many situations in which software must provide proper support _now_. For example, entry of expiration dates may not be accepted by a program. Cash-flow projections might be impossible past 1999. Many, many other examples can be found.

Solution: identify such software, then replace or fix it, whichever is cheaper.

This can consist of rewriting modules in in-house software, begging and pleading with suppliers to fix their software, or finding suitable (i.e. working) alternatives and purchasing new software. Printed and softcopy forms will have to be revised. The cost of fixing the problem will steadily increase as time goes by.

 Peter HANSEN                                     Engenuity Corporation
 peter_at_engcorp.com                              Guelph, Ontario, Canada