Some testing is warranted. However, I believe that tables created with FoxPro 2.6 would not automatically be converted to the VFP format. You must take care, I believe, only when creating tables with VFP7. You can also convert them back with the COPY TO ... TYPE FOXPLUS command.

In Visual FoxPro, you may want to SET CPDIALOG OFF, to avoid the nasty dialog box (which may or may not appear, depending on whether the tables are already marked with a codepage).

Regards, Hilmar.

>I'm working on converting an application from FoxPro 2.6 to VFP 7.0 However, the tables are used by (at the present time) and indeterminate number of other systems and applications. As a result, I want to insure that the tables are NOT changed from 2.6 to 7.0 format. As far as I can tell, the version is identified by the first byte in the table header record. I've identified the following possible solutions, any input on these or other solutions would be appreciated.
>
>1) Have the VFP app switcheroo copy all the tables to a 2.6 version when the user exits.
>
>2) Create a function or the like that, when 2.6 fails to open the table, will rewrite the header record to identify the table as a 2.6 beast.
>
>Respectfully,
>
>John