[jpsb]

But shouldn’t we be preparing now for Y3K?

No, but there is the Year 2038 problem

[George from New England]

I still live with the y2k bug.

I have some programs that I no longer have the source code to.

So to run them I have to set my p.c. clock back to 1999 and xeq them. They run fine after they start with the clock in 2017.

btw

[discostu]

And if programmers go back to lazy 2 digit years the next problem will be 2100. Because of the catchy name people think the problem was the 1 turning to a 2, it wasn’t, it was the 9 turning to a 0, and 0 turning to 1 can do the same thing if the coders of the mid century aren’t smart.

[SeekAndFind]

RE: No, but there is the Year 2038 problem

For those who want to know...