Note This feature is available when the Use advanced tools general preference is selected. See Using advanced tools.
For your solution to display in Kiosk mode, you must:
•create an account with a limited privilege set or create a specific Kiosk account
•clear the default option of logging into the file with the Admin account
•enable Kiosk mode
1. Create a new FileMaker file account.
See Editing FileMaker file accounts.
2. Create a new privilege set.
See Creating and editing privilege sets.
3. In the Edit Privilege Set dialog box, give the privilege set a name and description.
4. For Layouts, Value Lists, and Scripts, select either All view only or All no access.
5. Clear the Manage extended privileges checkbox, select other options as required, then click OK.
1. Close all database files that you are going to customize.
2. Choose Tools menu > Developer Utilities.
3. If you have used the Developer Utilities on the same database solution before and saved your settings, click Load Settings.
4. Click Add to locate the files that you want to customize.
5. If you add multiple files, double-click a file in the list to specify the primary file.
6. Select Developer Utilities settings as required. See Setting up files for developer solutions.
7. For Solution Options, click Specify.
8. Select Enable Kiosk mode for non-admin accounts.
9. Select other options as required, click OK, then click Create.
See Specifying options for developer solutions.
You can quickly repeat this process by clicking Save Settings and choosing a folder and location for your settings file. See Saving solution settings.
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.
1. With the database solution open, choose File menu > File Options.
2. In the Open tab, clear Log in using.
3. Click OK.
•Kiosk mode is ignored if the solution is opened by accounts with the Full Access privilege set.
•To ensure that users can access the primary file and quit the application cleanly:
•In each auxiliary file, provide a startup script that opens the primary file.
•In each auxiliary file, place a Main Menu button that runs the startup script to open the primary file.
•In the primary file, include an Exit button.