Im looking for a file format that does not truncate, saves the fieldname so that i can use the matchname on import and can be used with mulitple scripted imports to seperate tables.

Suggestions ....

To make matters worse the user will choose which file to import and this info set to a variable via an insert into a container and then a get as text calc to set the file location/name.

This is then used in the import scripts.

How about exporting to the FileMaker format. Seems like a good choice to me since DIF truncates after 255 characters (if I remember correctly). Or, how about skipping the export and simply importing from one FileMaker table to another? FileMaker will import only the currently found records from the source. Import will work even if the tables are in the same file. And, you can even use a script variable to select the file from where you are importing without needing to display the open dialog. You can see this technique in action by downloading this file:

http://www.filemakerpros.com/SAVEDYN.zip

While this technique shows how to save a PDF to a specified directory with a name from a field, the concept can be applied to any script step that specified a path.

tried using the fp7 format for some reason filemaker didnt like it. Export from seperate files via a gui(using seperated model) works fine and produces a file with one table.

It would import the records for the main first file exported but not the fields from the second file.

I have global table in main file with field ExportName.

Every time I export data this field is set to name of exported file (exmpl. Backup_2006_09_20.fp7).

When I run scripted import, user can choose file form which wants to import data. Then I first import globals table containing ExportName (which replaces value in ExportName field in main file), set variable $_filename to ExportName and then you can import records from all tables passing $_filename in "Import Records" script step.