Creating Kiosk custom apps
Note This feature is available when the Use advanced tools general preference is selected. See Using advanced tools.
For your custom app 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
To create a limited access Kiosk account:
-
Create a new account access entry.
-
Create a new privilege set.
-
In the Edit Privilege Set dialog box, give the privilege set a name and description.
-
For Layouts, Value Lists, and Scripts, select either All view only or All no access.
-
Clear the Manage extended privileges and Manage accounts that don't have Full Access checkboxes, select other options as required, then click OK.
To enable Kiosk mode:
-
Close all database files that you are going to customize.
-
Choose Tools menu > Developer Utilities.
-
If you have used the Developer Utilities on the same custom app before and saved your settings, click Load Settings.
-
Click Add to locate the files that you want to customize.
-
If you add multiple files, double-click a file in the list to specify the primary file.
-
Select Developer Utilities settings as required. See Using the Developer Utilities.
-
For Solution Options, click Specify.
-
Select Enable Kiosk mode for non-admin accounts.
-
Select other options as required, click OK, then click Create.
See Specifying options for the Developer Utilities.
You can quickly repeat this process by clicking Save Settings and choosing a folder and location for your settings file. See Saving settings for the Developer Utilities.
The Developer Utilities copy the selected database files to the Project Folder.
To change the default option of logging in to the file with the Admin account:
-
With the custom app open, choose File menu > File Options.
-
In the Open tab, clear Log in using.
-
Click OK.
Notes
-
Kiosk mode is ignored if the custom app 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.
-