Exporting Records From Tables

[SteveS]

I have a database that consists of 5 tables. I want to design a script for my end users that will export all records to a specified folder. I tried to accomplish this task and tested out my export script. The first table exported the correct amount of records. The other tables contained the same amount of records as the first table, even though they contained additional records. I know I am missing something simple with this task, I tried the “show all records” at the beginning of the script and that did not work.

Any help on this matter would be appreciated.

Thank You,

Steve

[comment]

Go to a layout of the source table before exporting.

[SteveS]

I tried going to each layout and then specifying field order to export and got the same results. One record or one table shows the exported records. I want one Filemaker Pro output file to contain all tables with associated records. When I set up the script to “Export Records,” the exported result is the first export records request and only the first.

[comment]

You can only export from one table at a time (although you can include related fields). What is the format of the export, and what is it intended for?

[SteveS]

I designed the FM 9.0 Advanced runtime program consisting of five related tables. The program is installed on a network server. The same program is also installed on 4 laptops with 4 users. I want to format a button available on the opening layout that will enable the end user to export all updated records onto a thumb drive, floppy 3 1/2 disk, or other folder location.

I also want to include a button on the program installed on the network server. The script for this button would be to import the above described updated records into the program.

I just wanted to automate this process for the end user.

[comment]

You need to save each export to a separate file. Even if you could somehow cram them all into same file (say by using a plugin), Filemaker wouldn't know how to divide the data in order to import each set into its own table. There's no problem with automating five consecutive exports within a single script. Same with imports.

Not related to your question, but synchronizing data that way can be VERY problematic. What happens if two or more users have modified the same record?

Also, you speak of installing a runtime on a server. I trust you know that runtimes cannot be shared?

[SteveS]

Comment,

Thank you for taking your time to help me on this matter.

I guess I will just have to make a scripted button available on each table/layout with an export / import scripted button included.

I know the runtime cannot be shared by consecutive user’s, this is why I wanted to find an way to automate this process. Export the records from the user’s laptop computers and import the updated newer records on the program installed on the server. All of the records have a unique id which will not change, just additional records

[comment]

I guess I will just have to make a scripted button available on each table/layout with an export / import scripted button included.

I don't see why you can't have a single button to perform a single script that goes to a layout of the first table, finds the necessary records, exports them to file #1, then goes to a layout of the second table, finds and exports to file #2, and so on.

[SteveS]

I tried the single button with attached script and it worked fine! I named each output file with a path going to the windows temp directory to perform without a dialog. I thought this location would be appropriate since all users would have access to the files for import.

THANK YOU!