This is typical of what I have seen with Y2K.
I'm sure you'll hear this client announcing that they have met their
deadline and are now
"Y2K Compliant".
It's been that way with both of the previous Y2K projects I worked on.  One
was only
about 80% complete when management declared victory, pulled the plug on the
Y2K budget and let the Y2K project team go.
Of all the programmers I know I have not yet heard one of them report that
their
company has done a proper and complete Y2K remediation.
(These are the same programmers that are buying generators and stocking up
on
food and water.)

Jim Mc Coy



----- Original Message -----
From: Cecile Chi <[log in to unmask]>
To: <[log in to unmask]>
Sent: Sunday, October 10, 1999 6:26 PM
Subject: No Y2K testing


> A client of mine was considering TimeShift for aging data to use for
> Y2K testing.  TimeShift did not handle the integer dates returned by the
> CALENDAR and HPCALENDAR intrinsics.  Gordon Helm, the vendor,
> added this capability, and I tested it - it works just fine!  Then my
client,
> still working on a plan for Y2K testing, received a corporate
> directive that all Y2K testing must be completed by November 1st.
> The managers promptly decided that there is no point in buying
> TimeShift now, because there isn't time to test anything anyway.
>
> I did not make this up - I'm not that creative.
> This is not an urban legend.  I was there, I heard the discussion
> and the conclusion.  I'm not sure I believe it myself.
>
> Cecile Chi
>