>>>Q2.
>>>is it (Dos) VF26 was Y2K ready ??
>>
>>No; there are add-ons like Communications Horizons Y2KFOX that will provide a workaround, but FPDOS by iteslef (without lots of code fixes) is not Y2K compliant.
>
>Did you know some problems with CENTURY ON and DATE Data Type handling only ?
>

Yep; without some workarounds, FPDOS 2.6 doesn't think February 29, 2000 is a valid date. This is not the only problem. There are kludgy workarounds; Y2KFOX/DOS, by loading a TSR before the runtime/development environment, works correctly 100% as far as I tested it. We used it to get around Y2K issues at Weatherhill until we managed to get everything ported to VFP and tested for compliance.

For us, it was worth the ~$995 price for a site license to buy us 10 months of development time extension, with a total investment of less than a day with Y2KFOX to read the docs and modify all the system startup behaviors (btch files and shotcuts) throughout our LAN. YMMV.