Edgar,

I'd *definitely* create an import routine! You should be working on this as your defining the new table structure, when the specific requirements are on your mind.

As for the "Table belongs to ..." messages... you can guarantee that they don't happen by first exporting all you data to free tables and importing from there...

Just my $.02 worth

HTH

>Looking for suggestions ---
>
>A project has been recreated - each table expanded with new fields.
>The existing 'compiled' VFP app will be replaced with the new one BUT I must retain all existing records. When time to activate the new app will an "import of old records" routine be required in the new app? Can I expect those errors such as TABLE belongs to DBC such and such? Is there an Easy way to make the transition.
>
>The main application exist on LAN (multi-user). A copy of the application is on a stand-alone in a remote office. VFP3 ...