Developer’s Guide

Distributing your bundled solution 4-11
Each time the runtime application is opened, it looks for the primary file
that has been bound to it. If the primary file can’t be found, the end user
is asked to locate the primary file.
Caution your end users that they should not rename the primary or
auxiliary solution files. If they do, relationships and external scripts may
not work properly. They can rename the runtime application after it has
been installed.
Note When you make a change to your solution, you should make sure
that your end users can import their data into your updated solution.
Include a script attached to a button to make it easy for your end users to
import their data into the new solution files. For more information, see
“Converting and upgrading solution files” on page 3-16.
Updating a solution
To make feature enhancements, modifications, or add solution files, you
must rebind and redistribute your runtime solution. If you are adding
more files to a runtime solution, bind new files with the original key used
when you bound the primary file.
Note To update a primary file, the filename and binding key must be the
same as when you originally bound the file. If you change the name of
the primary file, distribute a new version of the runtime application.
Updating the primary file
To update a primary file:
1. Open the original primary file in FileMaker Pro 4.0. Make the
changes to the primary file.
As long as the key and the filename have not changed, you don’t need
to rebind the primary file.
2. Send your end users a copy of the new primary file.
3. If necessary, create scripts that import end users’ existing data into
the new primary file.
Adding new or changed auxiliary files
To add new or changed auxiliary files, rebind the solution files and
generate a new runtime application. Use the same binding key that you
used for the primary file. Remember that the binding key is
case-sensitive in the Mac OS.