After generating your run time file, take a copy of it (you can change the extension back to FP7 if you want) and use that copy for future upgrades. Then, when you are ready to deploy an update, simply make a copy, change the extension back and swap files. This copy will retain the bindiing key added during the original run time creation. This will update the file's design, but any changes to data made by your users since the last update will be lost.
To preserve data updates, you'd still need to run your import script. If you choose to use a data separation model where one file has all your layouts, scripts and value lists while a second file stores the data, you can deploy a very large percentage of your updates just by swapping the interface file with all the layouts etc--leaving the data file unchanged.
I will lay around with this for a while. I am told that the FM data separation databases do not function as good as they should... is this correct?
What do you mean by "do not function good as they should"? Haven't heard that comment before...
I am currently trying to test a runtime upgrade. I am using the steps below, which I found under Filemaker help.
However I am having trouble understanding them. To clarify in step 2 does this mean to dump the whole folder from the old runtime into this new "old solutions" folder? And for the script, by extension does it mean the unique extension I created ".srt" or should this be the original "fp7"? Lastly I did get the script to finally take me to an import screen, however, it will only import fields for the table that layout is associated with, and only manually. I thought these instructions were for an "automatic upgrade of the runtime" and a full data import from the old runtime (meaning multiple tables at once). My customers for this are students and they are not going to want to do manual imports every time they upgrade.
If you have done this or have any ideas as to how to do this I would appreciate the help. I am still an amature developer so I appreciate the assisstance!1.3.