Using $variable to script import

[Simon Clement]

For some time now I have "automated" client updates of files through these steps.

First run a script that asks the user to "open" their old file. The old file is then imported into a container field and a related calculation field returns the path that is then set to a variable ($import).

The script then steps through layouts deleting records and importing records from the old file using $import as the file path.

This works fine as long as I've previously "trained" the script using explicit file paths. I then replace the explicit paths with $import.

I have a problem where this sometimes does not work for one of the import steps and I can't work out the logic as to why it might fail.

I'm using "Match field names" as the import criteria but wonder what might break my approach.

Adding new fields to the new file? (Field names are never altered once created btw).

Changing a layout name in the new solution?

Importing from a table in the old file with no data?

Any thoughts would be appreciated as when this works it's a lifesaver.

Regards

Simon

Simon Clement

Arawak Database Solutions

1/340 Main Street

Mornington 3931

Tel: 0359 758782

Fax: 0359 770150