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, Enable Database Encryption (or Re-encrypt files), and Remove Database Encryption. |
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. |
Force accounts without full access privileges to open your solution in Kiosk mode | Select Enable Kiosk mode for non-admin accounts. |
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 •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. •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. |
Encrypt or re-encrypt database files | Select Enable Database Encryption (or Re-encrypt files). Note This option is not available if you select Create Runtime solution application(s). You can use this feature to encrypt database files that are not bound to runtime applications. |
Decrypt database files | Select Remove Database Encryption. |