Well, Calvin, I would say that you have mis-assumed - " if century were set off and a 21st century date were typed in the system would know that the system date was the 21st century .

You want to sue people because you didn't read the documentation (which is brief, but says: "SET CENTURY OFF specifies a two-digit year format that includes eight characters and assumes the twentieth century for date calculations. This is the default setting.").

Seems pretty clear to me!

You might want to check when the SET CENTURY TO came into the language. It may have been FP 2.6, but I really don't know (head crash a few months back eradicated my FPD 2.6a copy and I didn't reinstall). If it was 2.6, then that is a relatively painless upgrade from 2.5

Jim N


>I have a vertical market app written in FoxPro 2.5 for DOS. I had assumed up to this point that the Y2K problem would go away when the century actually turned over, in other words that if century were set off and a 21st century date were typed in the system would know that the system date was the 21st century and everything would be OK. Now, I ( am I the last idiot left ) find out that FoxPro DOS itself is locked into the 20th century. It does not recognize the 21st Century system date. I now understand why Microsoft is being sued over this. Why have they not provided a patch for this problem. I am in the process of moving users to a VFP version of the product but they may not chose to convert. They may instead chose to sue us for selling them a product that does not even know what century it is in. I forsee a large number of law suits directed against Redmond if they do not fix this problem!