Importing data from one FileMaker database to another
FileMaker's import features are handy for entering a lot of data quickly, but sometimes the built-in import features aren't enough.
When you need to do repeated imports, or if your data needs to be modified before being imported, save yourself a lot of headaches and create a separate database to do the importing.
There are many advantages to this method, including:
- Keep the production file clean by building scripts and layouts in the importer file
- Data can be transformed in the importer file, in case the data structure of the source and production files is different
- Scripted processes can be set up ahead of time, so that complex imports can be done with the click of a button
- Data and production files can be swapped out as often as needed (as long as the file names are the same from one version to another)