>Hi Bruce,
>
>I don't have the luxury of simply changing the table structure and copying the database and changed file to a new
>directory. My situation is there's historical data that must be retained, the file structure of the old table is different
>and there's new indexes to be setup. Maybe if I had a blank changed table in the database to start off I can pass
>the old file setting up the changes to some of the fields then append the old data to the new table, would that be
>a better approach to this ?
>

A much better solution is available - Stonefield Database Toolkit, a commercial add-on for VFP, lets you propagate changes to you tables, indexes, views, relations, etc, from a set of metadata tables that it builds describing the current state of the DBC. It handles exactly what you'd like to do, as well as providing very solid reindexing, packing and simple data file repair tasks. It also provides a mechanism to extend the .DBC functionality based on the DBCX2 extensions supported by a number of other products like MereMortals framework and FoxFire! Most framesworks provide hooks to make adding SDT to their environment easy to do - certainly that's the case with Visual MaxFrame, and the CodeBook-derived frameworks such as MereMortals that I've seen.