Whenever you move FileMaker code from one file to another, you need to do things in the right order. If you follow this checklist everything will work correctly when it is in the new file. Some of this stuff you can copy and paste or import. The rest you will have to manually copy. It’s not fun, but if you need to rebuild a bad file, merge two files together, or just get a code chunk from one file to another, following these steps can get the job done.
- Custom Functions – Copy and Paste or Import
- Tables – Copy and Paste or Import
- Graph – Manual Fix. Make sure relationships and names are setup correctly
- Adjust Fields – Any fields that needed relationships will be need to be adjusted. One way to do this is to delete all the fields and re-copy and paste the fields from the old file to the new. That will break relationships, but those might be easier to fix than all of the broken calcs.
- Layouts – Manual make the layouts with the correct names. Skip content for now. That comes later
- Scripts – Copy and Paste or Import
- Value Lists – Manual
- Themes – Import ( Technically these can go any time before step 9)
- Layout Contents – Copy and Paste content, manually set sizes and parts.
- Layout Based Script Triggers – Manual
- Security ie Accounts and Privilege Sets – Manual
- Custom Menus – Manual
- File Options – Default Passwords and Window Based Script Triggers
Yes, this is tedious, time consuming, fragile process. But it is the best we have. In the case of smaller code chunks that have been designed with this in mind, like modularfilemaker.org modules, it can be made to work.
Click the 'Downloads' button above to get the Checklist For Moving FileMaker Code downloads.
We ask you for your email in exchange for downloading these example files. It helps us judge what types of content and examples our customers or potential customers are interested in. If you have an account and are logged in you will not have to enter your email and password again.