>>>Hi!
>>>How can I check or make sure that the tables on a foxpro 2.6 for windows application is compliant to the 2000 year, if not some one can give me a quick road map to do this by my self
>>
>>William,
>>
>>All tables in all versions of Fox all the way back to FoxBASE+ are year 2000 compliant. Date fields store the full four digit year.
>>
>>Your code may not be 2000 compliant though.
>Jim,
>
>So if I do check the part on the code that refers to "set century" and made it "on" if is not, that could give me the assurance of a 2k compliant code?


Yes and no. It really depends on the level of compliance. To be fully compliant, all dates need to be displayed and printed using 4 digit years. Simply doing a SET CENTURY ON will do this, but will the fields be wide enough to display/print?

Also, if you have any date constants in your code, they will be set based on your setting at compile time.

You need to be careful with the LUPDATE() function. It uses a few bytes in the DBF header, which are stored only with a two digit year.