Although I know that software on PCs could be date sensitive, I've never claimed Y2K was a PC problem. This is critical when I'm trying to pull off the DGI-to-GI conversion in an effort to avert some pain. the key question: Does the apparent backtracking by Microsoft suggest that the PC component of the problem looks substantially larger now? The day after the microsoft post earlier in the week, a friend informed me that our ComSci department was doing a very quick scramble within the computer labs to straighten out some problems. Opinions of PC-familiar remediators especially appreciated.

-- Dave (aaa@aaa.com), December 17, 1999

Answers

I work (and have worked) on mainframes, minis and PC's. I can use 2 digit year dates in my VB applications just like I can on a our minicomputer or on a mainframe for that matter. As you may know, my VB programs can look at data on a non-compliant minicomputer. It doesn't give a hoot. Our PC staff IS making y2k updates on various PC software. Don't ask me what, they are in charge of this not me. I hear this every so often. They are not done. These are the same people that told me I was nuts for taking y2k seriously a couple years ago. It's not so funny now. They are having to deal with it now while I can sit back with my fixes already done. I'll be out of the city, because there's no need for me to be present. My applications use 4 digits. They will work and there is no need for me to be present. Funny that government can't say that. I can guarantee my work, but they can't. This should tell you something.

-- Larry (cobol.programmer@usa.net), December 17, 1999.

FWIW: Karl Feilder, CEO of Greenwich Mean Time and a leading advisor on Y2K and PCs to the British, Australian, and South African governments, just went to a 9 on ye olde Y2K impact scale. A year ago he was at a 5. Something uncovered in his research and world travels during the past year has discouraged him, evidently. Mr. Feilder is so well respected that he serves as the chief consultant on the subject both to Action 2000 and to Task Force 2000.

-- Don Florence (dflorence@zianet.com), December 17, 1999.