Help

Using FileMaker Pro Advanced tools
F
ILEMAKER PRO HELP 605
13. For Delay, set the number of seconds that you want the splash screen to display.
You can preview the effect that your custom splash screen will have by clicking Preview.
14. Select other options as required. See Specifying options for developer solutions (FileMaker
Pro Advanced).
15. Click OK.
16. To be able to quickly repeat the process, click Save Settings, and choose a folder and
location for your settings file. See
Saving solution settings (FileMaker Pro Advanced).
17. Click Create.
Notes
• Setting the binding key:
• If you need to add auxiliary files later to the existing runtime database solution, rebind
the files using the same key.
• Use a binding key you’ll remember and record it in a safe place. (You can do this by
saving the Developer Utilities settings file. See
Saving solution settings (FileMaker Pro
Advanced)) If you forget your binding key and want to change a runtime database
solution, you’ll need to rebind all of the database files using a new binding key and then
redistribute the entire solution, including a new runtime application.
• You can open a bound runtime file in FileMaker Pro and FileMaker Pro Advanced to make
modifications to it. However, if you selected the Remove admin access from files
permanently option when you bound the files, then you can’t regain access to some
features. See
Removing Admin access to databases (FileMaker Pro Advanced). In this
case, you’ll have to open the original database files in order to make design changes in
FileMaker
Pro Advanced and then rebind them using the binding key that you assigned to
that runtime database solution.
Related topics
About creating runtime solutions (FileMaker Pro Advanced)
Naming runtime solutions (FileMaker Pro Advanced)
Distributing runtime solutions (FileMaker Pro Advanced)
Importing data into upgraded runtime solutions (FileMaker Pro Advanced)
Starting runtime solutions (FileMaker Pro Advanced)
Recovering runtime files (FileMaker Pro Advanced)
Naming runtime solutions (FileMaker Pro Advanced)
The filename extension associates all of the runtime solution files with the runtime application. If a
user has more than one runtime database solution on a machine, the filename extension together
with the binding key will ensure that the correct runtime application is started when a solution file is
double-clicked. Use an extension that is unique to your users’ computer systems.
Consider the following points when naming runtime solutions:
• The runtime name that you specify in the Developer Utilities is used for the name of the
runtime application and can also be used for the name of the new solution folder that
contains the bound runtime database solution files.
• Filenames can include up to 31 characters. When choosing filenames for runtime database
solutions, consider the platforms on which your runtime solution will be used so your scripts
and lookups will work properly.
• Use the default extension .fmpur or type a one- to five-character extension.