georgetirebiter writes: "At least one large, very successful financial services organization in the last few days fell victim to the Unix year 2038 problem when trying to create a standard 30 year risk contract in their proprietary financial software. The problem occurred when trying to make a standard time call in sql. I wonder how many other programmers have had to try to solve this problem in legacy systems? What solutions did they use? Is this really an incipient and perhaps more serious successor to the Y2K bug?"