Hello

My data migration app is progressing, but I know that a lot of my clients have made copies of various tables over the last 6 years that I have used
DBISAM - such as 'Copy of Address.DAT'. I have a list of kosher tables, and I guess I can rename the tables that I don't want to import into
ElevateDB, but I am not sure if that is the way to go.

I renamed the extensions of some of the non-standard files to 'Copy of Address.DATx' & 'Copy of Address.IDXx', but still had an error message (in
the IDE only) about the fact that ''Copy of Address.dat' wan't in the list.

Is there a better way to handle this situation? I don't want to delete the tables, but I also don't want to waste time converting tables that won't be used
in EDB.

Regards & TIA

Peter

Peter,

<< Is there a better way to handle this situation? I don't want to delete
the tables, but I also don't want to waste time converting tables that won't
be used in EDB. >>

This is on our list of enhancements, I'll see if I can move it up for you.

--
Tim Young
Elevate Software
www.elevatesoft.com

Peter


What I did was to copy the desired tables to the new location, run the migrator and then delete the old DBISAM tables. It's not much programming and it give the good old belt and braces to compliment the natural ability of a user to do a backup before starting anything like this.

Roy Lambert [Team Elevate]