>Does anybody Know if Foxpro for Windows 2.6 have problems with year 2000?, and where I can get fixes for this problem.
>
>Thanks
Yes, it does have problems.
If you have a user-entry field on a form, and you have a date field
for them to enter, and if they omit the century (i.e. they type in 12/15/01),
FoxPro assumes (always no mattter what you have setup in code) that the
century is 19. No matter what. So, you have to write a function which you
call that compares the year century entered to the actual system date century
and then give the user the option to choose the century (since it may be Jan 2000 and they might be entering data for 1999).

MS was sued just over this. The girl that sued them was correct.
MS FoxPro programmers hosed up here, they certainly have a hard coded
century setup instead of getting the century from the system. They should
have lost that lawsuit but the judge declared it worked as documented.
I know because I had to write a function that did just that - and I easily
got the century from the current system date - foxpro has the ability to
get it - the MS programmer just had no vision.

The programmer who coded that should hang his head in shame. I mean it.
I recall an old excellent programming book "Programming Proverbs" and there
was a phrase in that that I am paraphasing that went something like:
"If the programmer refuses to write good code, he should be taken out and
shot. If it is inconvenient to shoot him . . .".

This flaw in FPW reminds me of that quote.