Y2 NOT OK everywhere

Hi folks,

While the talking heads on TV and the radio talk show hosts all proclaim
how easy and uneventful theY2K transition was and how it was probably
all just overblown hype by consultants to make money....THIS consultant
has been busy with a client in serious crisis.

Yes, the client was warned verbally and by two certified letters that I
thought there was a high likelihood of serious system failures in the
custom code left by previous developers with the coming of Year 2000.
The client, however, absolutely certain I was intent on draining her
company's coffers needlessly, decided that "we'll fix it when it
breaks". Well, it broke, BIG TIME around early December!

As in Payroll wouldn't accrue and Accounts Receivable wouldn't bill into
January. Not to mention that on January 3, some subsidiary systems fed
12/31/2099 into the G/L and others fed 01/31/1900. (The G/L is a
purchased app and was updated by the vendor's Y2K release over a year
ago with 8 digit dates.)

The users are going crazy!!! As for me, I'm calm as can be. Why worry?
The work will get done. Eventually. However, I don't think the year end
financials are going to be quite on time.

I DO wish I could charge an "aggravation surcharge" in my rates, though.

Randy Mangham
Pacific Crest Consulting
San Diego, CA

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---