I did a little checking into the docs. Accordingly:

The smallest valid date in Visual FoxPro 6.0 is {^0001-01-01}, January 1st, 1 A.D. The largest valid date in Visual FoxPro 6.0 is {^9999-12-31}, December 31st, 9999 A.D.

Thus, all the 0000 dates should be considered invalid. Curious that although dates earlier than the year 1 are supposed to be invalid, they aren't. I guess the only solution is as you suggest and to do the check in the valid (maybe in a base class).



>>George;
>>
>>With strict date level set to 1 from options NOT A SINGLE ONE of the print statements below printed. I either got an invalid date message or an ambiguous date message.
>>
>>However, setting strict date level to 0 produced the same results you outlined below.
>
>Hi Bob,
>
>The STRICTDATE setting, of course, applies only to constants. I neglected to mention that I had the setting at 0 in my tests. The real problem here is that 3/1/0000 (or 3/1/000) when entered into a text is changed to 3/1/1900 when the StrictDateEntry property on the text is set to 1. OTOH, 2/1/0000 evaluates to invalid.