Agree completely. If she is stating her suit on VFP 3 and earlier versions of FP, she doesn't have a leg to stand on. As M$ stated SET CENTURY has been available since 1992 but Y2K compliance was not actually stated until VFP5. Some people just boggle the mind.

>Well, in FP, you have to enter 4 digits or add code to handle each field with a two digit year...or add code somewhere to covert the years to the appropriate century. VFP 3.0 doesn't have ROLLOVER in the SET CENTURY, so code would have to be added to the LostFocus or Valid method in the date entry class. VFP 5.0 has ROLLOVER, so everything is fine.
>
>This person really missed the boat. She should be using one of many other platforms that really do have problems because they don't store century information in their date fields. Maybe the choice of FoxPro stems from a loophole in the Licence Agreement rather than a problem with the platform? Because VFP handles Y2K problems as good or better than anything I've seen.
>
>Joe
>
>>
>>Exactly. The way this looks her claim should state, "I'm suing M$ because when I enter a 2 digit year in VFP it doesn't read my mind to know what century I meant!". She should wait until version 7, I here there is a new SET MINDREADING ON/OFF command included ;-)