This section is called "Import" in the Development Licence and "Test" in the Distribution Licence version. In the distribution version, instead of doing the actual imports, you're only running a test import to make sure everything works before building the distributed copy.
In the development licence you could be testing or importing, depending on which set of old files you choose.
The import tab is where the actual import happens once the setup is complete.
By choosing a copy of the live files ( like a recent backup or a local copy ) instead of the currently in use files, you can test the import as many times as required without interrupting the active users. Then when you want to re-run the import on the actual live files and put the completed imported files back into production you only need to alter the settings on the main Folders tab to point to the in use Live files.
1. Copy Files
This button will copy every file listed in the Files section from the Production data folder to the Control Folder, as well as exporting the Development files from container fields to disk. This step essentially gets you setup to run the import, with all the required files in place. The Live files are copied, not moved, so the originals are still there should anything in the import process not work.
In the Developer licence it will ask you to locate the Old files, so you can choose which copy to import from.
2. Perform Import
The Import button runs through the list of Tables in the portal below and does an import for each item. This has the following steps :
- Get the Record count from the Old table.
- Get the current Auto Enter Serial setting from the Old table.
- Go the the import Layout in the New file.
- Run an import from Old to New.
- Compare the Found Count ( the actual imported count ) to the Old record count.
- Compare the Total Record count to the Old record count.
- Set the New Auto Enter Serial value.
- Compare the actual New Auto Enter Serial value to the Old value.
This process checks all of the required items in each step of the process. Any errors are recorded in the portal, and the field changes from green to red. Any red fields are where errors occurred and should be investigated.
Common errors will be for Layouts that don't exist ( 105 - Layout is Missing ) or Tables that don't exist. If you get an error it should be fixed before proceeding to the next step that will replace your current live files with the imported copy. Fix the Table list, or check in the Old and New control files that all of the required items exist and that they have the correct names.
If you need to make any changes, you will need to re-run the 1. Copy Files step again afterwards.
3. Move New Files
If you're testing the import, you can skip this step, as you're just wanting to find out if the import works, not wanting to replace original files. Once you've tested, then you're selecting a live set of files not the backup and then you want to replace the originals and run this step.
The final step in the process is to replace the original files with your new development copy with the data imported. There are two steps in this process. First, the original file is moved to a backup folder. Second the imported file is moved into the Final Data folder, which by default is the same folder the files originally came from.
In the case of files hosted on FileMaker Server, the files are put back onto the server. If you're on a Mac, there will be a dialog asking for authentication. This is to set the permissions and ownership of the files properly so that they're able to be opened and edited by FileMaker Server.