Juan,

I dunno, does SET SAFETY OFF make a difference?

It seems it would be easy to programatically create a new table (in your database) with the same structure as the existing table, use the new table, and append from the old. This should avoid the message altogether.

Do have old versions of Fox that need to read the new table?

>
> Just as background, the table can be opened in VFO70 with no problem
>delete and add rows, no problem as long as is a fee table. now we decided to
>create a database and want to include 'on the fly', but I am getting the message below each time the command ADD TABLE table1.
>
>File 'users.dbf' will be updated to a new file format, making it unreadable
>to previous versions of Foxpro. This can be reversed with a 'COPY TO'
>command, and the old table will be saved as a .BAK. continue?
>
>
>I click , since I don't want to change the table's properties.
>I think this is related to the table's code page, but if I run
>the command ?cpdbf() the value is 1252 which is the same as
>?CPCURRENT(1).
>
>So how can I avoid this message?
>
>Thanks!
>
>

Steve Gibson