>>>>Hi Randy. My personal opinion on making a VFP app Y2K compliant.
>>>>- SET CENTURY ON
>>>>- widen your textboxes to have 4 digit year.
>>>>- do a search for every date function (like DTOS, DTOC...) and ensure the routines aren't making any assuptions about the century
>>>>
>>>>You are done. Other opinions differ though.
>>>
>>>Thanks Evan, That may be the route I take (with some people screaming that they can't enter 2 digits)
>>>
>>
>>No problem they can still enter 2 digit years. It will expand to 4 as they leave the field, giving them an immediate visual clue that it's the wrong century.
>>
>>
>
>Thanks Fred, I just tried it on a test form and noticed that. I may have to put up a larger warning on border line dates for my heads down data entry people.
>

Randy,
You also may want to review the SET CENTURY...ROLLOVER command for those "borderline" dates.


>Is the web page I mentioned earlier wrong about the century property for controls being in VFP 3.0? I found it in VFP 6.0, but not in 3.

I really couldn't tell you about VFP3, never used it all that much. The .Century property was also in VFP5, though, I think they changed the default value for it in VFP6.