First off, I am new to Filemaker. I am using FM Pro 8.

I have been tasked with creating an automated backup of multiple tables. What I have done is created duplicates of the tables (without our complicated layouts) and have created a script to import the data I want to backup into these backup tables.

What remains is exporting these tables into a single .fp7 file. If I export one at a time to the same file, it overwrites the last export and I have been unsuccessful in finding a way to export all the tables at one time.

What am I missing?

why not create a file with a copy of the tables and import directly into that one?

If you're using FileMaker Server: let that one take care of the backups... much less hassle.

Ok, that makes sense to me. I've copied the tables to a separate file. However, when I access that file from my script, how do I direct the records into the correct table? I am able to open a file but it seems I cannot switch to a layout within that file.

Forgive my lack of experience.

From what I'm gathering in my Internet searches, what I am trying to do may not even be possible. I cannot open a file from a script and then navigate layouts within that file.

Am I wrong?

You can open another file by a script, and you can call scripts in that file. However, I am not at all convinced that importing records over and over into the same Filemaker file is a good idea for a backup. Why don't you simply export each table as a text file, using the table name and the export date to name the backup file? The merge and the XML formats are good for this, as they keep the field names. You only need to use the .fp7 format to back up container fields data, if you have any.

That is in fact what I just completed. I was hoping for only one resulting file, but this works too - it's just not as clean as I would have liked.

It's possible (though not exactly easy) to combine the files, but keep in mind that when restoring the backup, there is no way to import into multiple table at once. So there is no advantage to having a single-file backup other than a neater backup folder.

That settles it then. Thanks.