>Q2.
>is it (Dos) VF26 was Y2K ready ??

The good news is that at the data level, the "date" data-type contains a four-digit year ("yyyymmdd") in all versions of FoxPro and Visual FoxPro. As long as you have used date fields rather than character fields to store dates, you won't have any fundamental data problems with any FoxPro or VFP tables.

However, there are still some issues to be aware of, notably those that relate to data entry and display of dates, as well as a handful of functions like CTOD and LUPDATE. There are a number of published work-arounds and third-party tools for dealing with some of these issues, like the one Ed mentioned.

I would encourage you to read the white paper from Microsoft entitled "Year 2000 Date Support in Microsoft FoxPro". You can find it on the MSDN site at http://msdn.microsoft.com/library/backgrnd/html/vfpy2k.htm. This will give you a good overview of the issues you will want to be aware of.

In addition, you can visit the Microsoft Year 2000 Resource site for FoxPro at http://msdn.microsoft.com/vstudio/y2k/vfoxproy2k.asp. This page has links for specific information about each version of VFP and FoxPro. The link for FoxPro 2.6 is http://www.microsoft.com/technet/year2k/product/user_view71777EN.htm.

HTH,
Rick