>>Then point the DBC to the new tablename when it asks to locate it.
>
>Is it possible to do this without user intervention? This should be in a standard upgrade procedure.

I wouldn't risk it. You'd have to hack the DBC to do so, I guess. You might want to look at Stonefield...

>Which is the best way to upgrade tables that are included in the DBC, without any danger of data loss?
>The Alter table command would be much more code intensive, and if a table got upgraded only partly (only some one of the new fields got added) this would be very difficult to track. By replacing the entire table this is much more secure, as we did with FoxPro 2.6
>
>Any ideas for this to do in a better way?

Not sure what you're trying to do here when you say "upgrade". Good planning means you don't worry about changing DBC-contained table file names very often. When I need to, I do it the way I described. Other changes, I use Alter Table.

BTW, Alter Table does create backup files, so it's got a built in safety. If there's a problem like running out of space, it will replace the original table automatically - I've found it pretty safe, anyway.