Hi Morys --

STRICTDATE does not enforce anything at the UI level, what it does is to cause VFP to error on compilation or runtime (depending on the setting) if any ambiguous data references are used. So, for example, if you had a CTOD() function somewhere or a date not in the format {^1999-04-19} then you would get an error.


>I already have my ROLLOVER set. I am a little confused with the strict date thing though, I thought that users were going to be forced to enter the four digits for the year if the SET STRICTDATE TO command was issued and I am NOT seeing any difference with it or without it.
>
>What is it that I am supposed to see different with the SET STRICTDATE TO command?
>
>
>>These properties are for Forms, Morys. It's a good idea to use the SET STRICTDATE TO and SET CENTURY commands at least once for the default datasession. Also, you need to use SET CENTURY to set your ROLLOVER.
>>
>>
>>
>>>In VFP 6.0 the Century property is by default set to 1 - ON and the StrictDateEntry property is by default set to 1 - STRICT.
>>>
>>>Question:
>>>If this is already set, is there anything that I am supposed to set in my program if I want to change to strict date? Is it everything ready for me or what am I missing?
>>>
>>>Thank you in advance.