Here's a thread that describes taking an existing file and converting it to a data separation model:
You can also use scripts to import data when that is necessary. The Script can even pop up an open file dialog where the user locates and selects the original file, then the script uses that info to connect to and import the data from it. This is often useful even with a data separation model should you find you needed to make changes to the back end portion of the file.
Thanks for your reply Phil,
I will have a look at it, however it is not neccessary to import data. It should be a live link to the data FMP file. This way i try to be flexible with chaning lay-outs while NOT having to import te data and perhaps to forget to import a table.
Yes it should, but if you have modify the design of the data file or the data file suffers corruption, you will still need to import data. The data separation model greatly reduces the need for imports but it does not totally eliminate the need to do so. Thus, a scripted import process is still a useful thing to build in to your database systems.