>>>Does anyone have any documentation or information about Foxpro 1.01 and Y2K compliance?
>>>
>>As far as I remember there is no change in table structure from 1.0 to 2.6. If it's correct then it's Y2K compliant too (except in all versions lupdate() function fail).
>
>Yes, in terms of date storage in tables. But of course there's the problem that it assumes 19xx in data entry (GET or BROWSE) when user types 2-digit year.
>
>Of course if you're asking about FoxPro 1.02 (was there a 1.01?), you must be talking about a legacy app *written in* FoxPro 1.02, surely you wouldn't be using it for new development ... and there's no guarantee that the programmer who wrote the old app didn't do lots of non-Y2K-compliant things when writing the code. For instance, did they make indices based on 12/31/99-DateField to sort in reverse-date order (I've seen it done). Did they store dates as three numeric or character fields (and/or variables) anywhere, and is all their code to handle that Y2K compliant?
>
>There are a lot of potential problems to look for when examining an old application for Y2K compliance. There are several tools written for doing this specifically in FoxPro (my company has written one). Just because the tool itself can be called mostly Y2K compliant, doesn't guard you against a bonehead who may have been using the tool ten years ago.

I meant the fox itself was Y2K compliant not the programs. It's even possible to make Fox 6.0 Y1K incompliant.
Cetin