Development Guide

10 FileMaker Pro Advanced Development Guide
10. Do one of the following:
1 If you want to create a copy of your database files with new names, click Create.
Note FileMaker Pro Advanced automatically updates internal links to related files and scripts.
1 If you want to further customize your database files or bind the files, under Solution Options, click
Specify.
11. In the Specify Solution Options dialog box, select one or more options:
12. Click OK.
13. To be able to quickly repeat the process, click Save Settings, and choose a folder and location for your
settings file. For more information about saving solution settings, see Help.
14. Click Create.
To Do this
Bind databases to runtime applications Select Create Runtime solution application(s).
Note This option can be combined with all others, except Databases must have a
FileMaker file extension.
See “About creating runtime solutions” on page 11.
Permanently prohibit any
administrative access to your solution
Select Remove admin access from files permanently.
Important Once removed, administrative access cannot be restored to the custom
solution.
For more information about removing Admin access to databases, see Help.
Force accounts without full access
privileges to open your solution in
Kiosk mode
Select Enable Kiosk mode for non-admin accounts.
See “Creating Kiosk solutions” on page 17.
Add the FileMaker extension to the
filenames of database files
Select Databases must have a FileMaker file extension.
Note This option is not available if you select Create Runtime solution application(s).
You can use this feature to add extensions to files that do not have extensions.
Create a log file to record any errors
encountered during processing
Select Create Error log for any processing errors.
Specify a location and a filename for the error log.
Notes
1 If you don't specify a filename and location for the error log, it will be saved to the
project folder with the filename Logfile.txt.
1 If an error occurs during the processing of the options, the error is logged in the error
log. An error message may also indicate that an error has been encountered.