>>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!
>You can make it work and not have to switch them to VFP. AFAIK, no FoxPro version before VFP6 (5?) has been labeled fully Y2K compliant.

VFP5 is branded as fully compliant. BTW, VB6 is still called 'Compliant with minor issues'.