Force Import to use matching table name

[Hijack]

All,

Anyone hit this scenario before?

If you have a complex database with many tables and want to be able to script a data migrgation into the newest version from an older version, you have to set up lots of "Import" script steps, one for each table. The import source filename is set in the script by user entry. To set each script step correctly you have to hard code the file name temporarily during script edit so you can pick the source table name and the field import order (in this case "Matching Names"). After that, you remove the hard coded reference and slide in your $variable reference you know the user will set.

My question is, if one table does NOT exist in the import source file you would think that FM would throw an error you could track. But, it just seems to default to the next table and pulls data in from there. When you set "Matching Names" on an import step, the next time you view the step it has reverted to "Last Order". Maybe that's because when I look at the step after I slide in the $variable file reference it can't access the file during script edit so it defaults to "Last Order".

Anyway.... Anyone have a better way of absolutely forcing FM to only import from a matching table name and matching field names during a script?

Thanks

David

Edited March 8, 2010 by Guest