>Does anybody Know if Foxpro for Windows 2.6 have problems with year 2000?, and where I can get fixes for this problem.
>
>Thanks

Jose,

Away from philosophy and an answer to your question:

A. Use Y2KFox (http://www.y2kfox.com/) or Fox2000 (http://www.compusolve-us.com/prod03.htm). These wrap around your code and make the problems quick to fix, though they are not cheap.

B. See Christof Lange's article "Y2K solution for FoxPro 2.6" in the files section (file cabinet icon) under "Coding, Syntax, and Commands." It has been updated somewhat since it was published in FoxPro Advisor.

I have been using this code for several months and it has done well for me.

In addition to setting CENTURY ON you will need to:
1. Widen the spaces on your forms and reports to show all 4 digits of the year. That is the only way dates will not be ambiguous.

2. Eliminate dates which are stored as characters in your data, or identify a reason why they are ok. For example, in a MEMO field for a sales contact database, "Called Harry on 2/29/00 and told him to pay his bill." would be ok with me since there will be no calculations performed on that date.

3. Notify your users (unless you have custom code that has a rollover feature) that any date entered with only 2 characters will default to the 20th century. That means typing "01/01/01" actually stores {01/01/1900}. Because of this, you may want to add some "reality check" code, like dDateOfSale can't be before {01/01/1990}. In order to store {01/01/2000} the user will need to type "01/01/2000."

4. Comb through your code for hard-coded CTOD()'s which use a 2-digit year and correct them. Be sure that any DTOC()'s will fit where they are supposed to now that they have 2 more characters.

5. Check for use of the LUPDATE() function. The LUPDATE function will always return a 19xx year in 2.6. This has been fixed in VFP 6 and a patch is available for VFP 5. This information is stored with only two digits in the table's header. Use FDATE and FTIME to get the date and time from the directory. That's what VFP 6 and the VFP 5 patch do.

Additionally, see the Wiki at http://fox.wikis.com/wc.dll?wiki~FoxYear2000Issues