>I don't think it's over blown at all.
>There's an awful lot of company's that have not started remediation yet.
>And there's an awful lot that have started, but are hopelessly behind schedule.
>I was working at one company that started having failures on 1/1/98.  They'll be
>dead in
>the water on 1/1/99.  They fall futher behind as their programmers are bailing
>out.
>This is an insurance company.  The company and their policy holders are in big
>trouble.
>Upper management really dropped the ball on this one and I know there has to be
>more in this situation.

We are one of those company's and it scares the heck out of me. Maybe that's
a little overblown, but there has been no real commitment to getting the
problem solved. We are replacing the aging handheld computers in our route
trucks, but it's really making more problems then it is solving. The payroll
and HR system are moving to PC's. Very very little has been done on our
homegrown code, and it's mainly done with date folding. I personally think
the best approach is to fix the databases to have the century added, if you
need to get into the code you should fix the problem not just use a
temporary work around. In some cases the date folding just doesn't work, we
have had some customers for over 50 years!

If resources are not put into solving the Y2K problem, I'm not going to be
here when 12/31/99 roles around. Anybody need a C or SPL programmer that's
been around the 3k since 4Qdelta2?

Lane