Developer’s Guide

40 FileMaker Developer’s Guide
To ensure that users can access the primary file and quit the
application cleanly:
1 In each auxiliary file, provide a startup script that opens the
primary file.
1 In each auxiliary file, place a “Main Menu” button that runs the
startup script to open the primary file.
1 In the primary file, include an Exit button.
For information about creating buttons and scripts that emulate
missing menu options and window controls, see “Emulating menu
commands and window controls” on page 41.
Creating Kiosk solutions
Kiosk mode is ignored if the solution is opened by accounts with the
Full Access privilege set, a privilege set that allows management of
extended privileges, or a privilege set that allows modification of
layouts, value lists, and scripts.
For your solution to display in Kiosk mode, you must:
1 create an account with a limited privilege set or create a specific
Kiosk account.
1 enable Kiosk mode. At the same time that you enable Kiosk mode,
you can bind the database as a runtime solution.
1 clear the default option of logging into the file with the Admin
account.
To create a Kiosk account:
1. With the database solution open, choose File menu > Define >
Accounts & Privileges.
2. In the Define Accounts & Privileges dialog box, click New.
3. In the Edit Account dialog box, type an account name, click
Active for the Account Status, and select New Privilege Set from the
Privilege Set list.
4. In the Edit Privilege Set dialog box, give the privilege set a name
and description.
5. For Layouts, Value Lists, and Scripts, select either All view only or
All no access.
6. Clear the Manage extended privileges checkbox.
7. Select other options as required.
8. Click OK.
To enable Kiosk mode:
1. Follow steps 1 to 9 in “Modifying database solution files” on
page 18.
2. In the Specify Solution Options dialog box, select Enable Kiosk
mode for non-admin accounts
.
3. Select other options as required.
4. Click OK.
5. 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.
6. Click Create.
If you did not bind the files to a runtime application, the Developer
Utilities copy the selected database files to the Project Folder. If you
did bind the files to a runtime application, the Developer Utilities
copy all of the runtime files to a new folder created inside the Project
Folder and named after the runtime solution.
To change the default option of logging into the file with the Admin
account:
1. With the database solution open, choose File menu > File Options.
2. On the Open/Close tab, clear Log in using.
3. Click OK.
Using scripts to control your solution
You can use scripts to automate much of your database solution,
control startup behavior, emulate menu commands and window