Developer’s Guide

20 FileMaker Developer’s Guide
11. Click OK.
12. To be able to quickly repeat the process, click Save Settings, and
choose a folder and location for your settings file.
See “Saving and reusing Developer Utilities settings” on page 25.
13. Click Create.
The Developer Utilities copy all the selected database files, with the
modifications made by the Utilities, to the Project Folder. If the
default option to overwrite the destination files has been left on, the
specified Project Folder will be used to store the files copied by the
Developer Utilities. If the default option to overwrite the files has
been cleared, the specified Project Folder will be used if it is empty
or a new one based on the name of the Project Folder will be created.
Creating an error log
Some errors do not trigger error messages. An error log will capture
more detail on any errors encountered during processing.
To create an error log:
1. In the Specify Solution Options dialog box, select the Create Error
log for any processing errors
.
2. Click Specify.
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.
3. Use the Specify a file dialog box to select a location and provide
a filename for the error log.
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.
Considerations for a runtime
database solution
You should address the following issues before binding the files to
the runtime application.
1 Do you want users to open and close auxiliary files?
In the runtime application, there are no menu options to open or close
files. If you want users to open and close auxiliary files, you must
provide scripts in your solution to perform these operations. In each
auxiliary file you must place a button or startup script that returns
users to the primary file.
1 Do you want users to be able to modify the database?
Unless your runtime database solution files are password protected,
users can open and modify the files in FileMaker Pro or FileMaker
Developer. You can also make your files permanently unmodifiable.
See
“Removing full access privileges from databases” on page 27.
1 Will this be a runtime database solution used on both
platforms?
See “Binding files for both platforms” on page 22.
1 How will you provide updates for your users?
You can make it easier for users to update your runtime database
solution files by providing scripts in your primary file to export their
data and import it into the updated solution. See
“Importing data into
upgraded runtime solutions” on page 26.
Add the FileMaker
extension to the
filenames of
database files
Choose 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
Choose Create Error log for any processing errors
See “Creating an error log” in the next section.
To Do this