Developer’s Guide

5-6 Developer’s Guide
1 Include information about the minimum equipment and software
requirements.
For suggestions on other information to include with your runtime
database solution, see “Including printed documentation” on
page 2-11.
Starting your runtime database solution
The first time users double-click the runtime application icon, the
runtime application will auto-register and move appropriate items
into the System folder on their machines.
In Windows, the three-character filename extension associated with
the solution will not be registered by the operating system until the
runtime application has been started. If a primary or auxiliary
solution file is double-clicked before the runtime application has
registered the extension, the runtime application won’t be found.
Important Your users should start your solution by double-clicking
the runtime application icon, not the primary file icon. Double-
clicking the icons for the primary or auxiliary files might result in
errors, depending on whether there are other copies of the runtime
application on the hard disk. If your users have more than one
solution on their computers with the same three-character extension
and they double-click the icon for the primary file, the most recently
installed runtime application is opened, which may not be the correct
application for your solution’s primary file.
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
user is asked to locate the primary file.
Caution your 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 users can import their data into your updated solution.
Include a script attached to a button to make it easy for your users to
import their data into the new solution files. For more information,
see “Converting and upgrading solution files” on page 2-17.
Recovering damaged files
Power failures, hardware problems, or other factors can damage a
FileMaker Pro file. If your database solution becomes damaged,
your users need to recover the damaged file. When the runtime
application discovers a damaged file, a dialog box appears, telling
the user to contact the developer.
Once you know which file is damaged, you can recover it—however,
the Recover command does not appear in the File menu of the
runtime application.
To recover a damaged file:
1 On Windows machines, press Ctrl+Shift while double-clicking the
runtime application icon. Hold the keys down until you see the
Recover File dialog box.
1 On Mac OS machines, press Option+3 while double-clicking the
runtime application icon. Hold the keys down until you see the
Recover File dialog box.
Double-click
to start
Runtime application icon
Primary file icon