Creating Kiosk solutions (FileMaker Pro Advanced)
• enable Kiosk mode. At the same time that you enable Kiosk mode, you can bind the database as a runtime solution.Note 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.
1.
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.
6. Clear the Manage extended privileges checkbox.
8. Click OK.
2.
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.
6.
7.
8.
9.
10. Click OK.
11. You can quickly repeat this process by clicking Save Settings and choosing a folder and location for your settings file. See Saving solution settings (FileMaker Pro Advanced).
12. 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.
1.
2.
3. Click OK.
• If there is no Quit or Exit button available in your Kiosk solution, users must force-quit the application by pressing Alt+F4 (Windows). With Mac OS X, users can exit a solution running in Kiosk mode by pressing F9 or F11 to access another open application window. Force quitting is not recommended because it can cause data corruption or damage open files.
•