There is no way to use a FileMaker script to initiate the switch.
Thank you Phil,
any other way without having attributes in tables?
"attributes in tables" means what to you?
It means to me that i could make a attribute code in each table and change its value via script. Then make a lookup on two external data sources. Depending on the matching code it would lookup related records from either one external data source of the other.
It would be theoretically possible, but very cumbersome to implement.
Very true indeed, my current plans are to manually relink all tables at the end of our six week cycle to the productive database. Would you have any other suggestions?
I just realized something. You don't have to go through Manage | database to make the switch. YOu can do this from Manage | External Data Sources.
In the external data source entries you can put a reference to your test data source first, the reference to your production data source second. You then need only remove the reference to the test data source and the file should redirect to the production data source. If you have all your data source tables in a single file, this could be an update of a single line of text in Manage | external data sources.
i tried what you wrote multiple times, but as soon as i remove the main mapped external data source it does not cut over to the production one. Both database files are identical. How are customer upgrades usually accomplished with Filemaker? Is it recommended to import the productive data sources and then overwrite the production system?
thanks to your help and some more testing i found a solution that works. This is most likely what you meant, but i will write down the procedure as i use now for others who might face the same challanges as me.
Switching between development and productive data sources
- Open the file menu
- Open the Manage submenu
- Click on External Data Sources
- Select your main data source
- Click on edit
- Change the file path from the development data source to the production data source
Is there a way to script this step?
Thank you Phil !
There is no way to script it, but if all your data tables are in a single file, this is not a terribly difficult task to perform.
The trick to avoiding this altogether is to place the front end on the server in the same folder as the back end. Then you can set up a single relative path reference in your manage | external data sources window that will work for the copy you are developing on and for the production copy. Deploying a new copy then is simply a case of swapping out the old interface file for the new unless your upgrade requires a change to the data file.