I did a similar thing where one server (client) would write it's records to a remote data source (provider) daily as a server scheduled script. The remote source was setup during the install process, but it would point to your central server.
What was neat about our solution is it had a built-in lock, meaning that it could disable the system or alert the provider unless the lock was cleared daily on schedule. Since you're already "phoning home" you can adapt this as your own personal license key if you want for your vertical.
The above scheme could be adapted for you, by setting up a temp table in your main database, and only giving access for your client's servers to write their records to that table. You could then process the records from the temp table into what you need.
Since you're dealing with potentially overlapping sources, make sure to use UUIDs as match keys, and not serial numbers.
How did you get the data to the Filemaker server?
Did you actually move it or import some other way?
No need to move the file. You can access the remote files as an external data source. File>Manage>External Data Sources.
There are other ways, but this has been easy for me.
Thanks Big Tom, I will try that
Yeah, what bigtom said, just as an external data source. Each client would have the remote temp table inside their file’s relationship graph.
You can transfer data from one file to another using Perform Script and a paramter or use Import/Export and a matching field UUID.
The Perform Script method is a bit tedious at times but it works with Photographs and BEST OF ALL it is easy to add new fields.
You do NOT need to add TOs and manage them. The receiving table can be anywhere and it needs one script for the Perform step and one script for the distribution of data.
I use this as a BLOB which I first encountered 20 years ago working on a 4th Dimension project. One BLOB of data could contain records from many tables and contain flags for various actions in the scripts. The idea was to transfer data to many user files with almost no user interaction involved.
Using this idea I am able to spend the day taking photographs of various properties and when ever I choose send those records to Momma (My Original Multiple Media App).
If needed the same BLOB can be sent to other computers with no extra effort.
Repeat: Using Perform Script (parameter) eliminates the need to add TOs and all that extra effort. If all of the files match, then one simple script (or not so simple) can be pasted or imported and do the job.
I've also been able to upload a blank file (no tables, no scripts) to a server and use another with scripts to create the tables in that file. Which means additional tables can be added at any time using a script.
I'm looking to create independent self sufficient files that log in to grab info, log out to go to work, and log back in to send the data to the storehouse.
Oh my, I just thought of a better way to design my IOS files...