
Two client's were not fixed in time because . .
. . their software vendors didn't get their fixes debugged in time. Both vendors had tried to combine the Y2K fixes with other stuff, and got behind on the release.
One, an auto mechanic shop specializing in Land Rover and BMWs, lost all customer service records for January and half of February 2000 because the database couldn't store them in a retreivable manner. I had updated his machine from Xenix (not Y2K compliant) to Caldera Linux in time, but he had to run the old software on it until mid February.
Another client, who refurbs and resells Nortel telephone equipment, had similar problems with his networked accounitng system. Reports were badly out of order and pretty meaningless until the fixed version was done (mid January). Fortunately, he didn't lose data and his reports were good after the fix. This was a DOS network system running with a Samba server.
The accouning system we used in-house simply prevented all access as of 1 Jan 2000. It had to be given a false date even to let you in to review old data, and could post no transactions beyond 12-30-99. Fixes were available in October but I did not install them because I was moving to a different system.
[link|http://www.aaxnet.com|AAx]