Folks,

VFP6 is much more robust in the Y2K area. There is a new command SET STRICTDATE whihc is involved with making applications very Y2K compliant. The syntax is listed below

SET STRICTDATE TO [0 | 1 | 2]

The Arguments

0 Specifies that strict date format checking is off. When STRICTDATE is set to 0, invalid Date and DateTimes evaluate to the empty date.

1 Specifies that all Date and DateTime constants be in the strict date format. Any Date or DateTime constant that is not generates an error, either during compilation, at runtime, or during an interactive Visual FoxPro session.

2 Identical to setting STRICTDATE to 1, but also generates a compilation error (2033 – CTOD and CTOT can produce incorrect results) whenever CTOD( ) and CTOT( ) functions appear in code.

The above is excerpted from the VFP6 Help file.