How does separation work?
"Separation" is a technique to isolate the data in a FileMaker solution from the scripts and interface. This is done by using separate files (separate .fp7s) for the interface and for the data. And in the case of SeedCode Complete, we have further separated the data into two files: SeedCodeData.fp7 and SeedCodeMedia.fp7-- this is done because the media file can get quite large over time and with them separated this way you can, for example:
But the real benefit of separation is that is makes it easier to make changes to your solution. This can be overstated, but in general, you may be able to take the interface file offline, make changes to it, and the redeploy it while your users continue to use your data file. Furthermore, you can likely send a copy of your interface and data files to your developer so that he or she can write some new scripts for you, and the developer could return a new interface file that you can deploy without having to import all your data back into the solution.
That is the goal, at any rate. Substantive new features may, of course, require changes to both the interface file and the data file. But separation does offer a good way to speed development of new changes once a solution is up and running. And if you do need to load up a new version of the data file, our "update" scripts can help move the live data into your new data file.
Check out SRF's description of separation for a nice overview of these same ideas.
Things to keep in mind.
So there are a few things to be aware of in a separated, or multi-file solution: