Developer’s Guide

4-8 Developer’s Guide
If you forget the original binding key for your runtime database
solution and want to update or add a file, you’ll need to rebind all of
the database files with a new binding key and redistribute the entire
solution.
To distribute an updated primary file:
1. Open the original primary file (before it was bound) in
FileMaker Pro.
2. Make the changes to the primary file. If necessary, create an
Import script so users can import their existing data into the new
primary file. (See “Importing data into an upgraded runtime
database solution” on page 3-17 for information.)
As long as the binding key and the filename have not changed, you
don’t need to rebind the primary file.
3. Send your users a copy of the new primary file with instructions
to replace the old primary file in the runtime database solution folder.
To distribute a new or updated auxiliary file:
1. In FileMaker Pro, create the new auxiliary file or open the original
auxiliary file (before it was bound) and make changes as desired.
2. If necessary, create an Import script so users can import their
existing data into the new file. (See “Importing data into an upgraded
runtime database solution” on page 3-17 for information.)
3. Use the Developer Tool to rebind all of the files in the runtime
database solution and include the new or updated auxiliary file. (See
“Procedure for binding files” on page 2-6 for information.)
Use the same binding key that you used for the primary file.
Remember that the binding key is case-sensitive.
4. Send your users a copy of the new or updated auxiliary file along
with instructions to place it in the runtime database solution folder,
replacing the old file if appropriate.
As long as the binding key has not changed, you don’t need to
redistribute the runtime application or other solution files.