>>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.


>By the way, the reason the textbox would not fire the error event is that this textbox was subclassed from a datebox in codebook 3.0. That valid event code was checking the date entered and returning to the textbox after formatting the date, so there really wasn't an error. Thanks for your help.