Help

Using FileMaker Pro Advanced tools
F
ILEMAKER PRO HELP 598
modified by anyone, including FileMaker employees. The only way to modify the tables, field
definitions, relationships, scripts, or access privileges is by returning to the original file before it was
customized by the Developer Utilities.
To remove Admin access to a database:
1. Close all of your 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 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
(FileMaker Pro Advanced).
7. For Solution Options, click Specify. See Specifying options for developer solutions
(FileMaker Pro Advanced).
8. Select Remove admin access from files permanently and click OK.
This prevents users from altering the design and structure of your database files and from
changing any accounts or privileges that you’ve set up.
Notes
• When the Remove admin access from files permanently option is enabled:
• Users can’t access these dialog boxes: Manage Database, Manage External Data
Sources, Manage Custom Functions, and most of Manage Security.
• The text version of custom functions is removed.
• Users can access the Extended Privileges tab in Manage Security if their account has
the Manage extended privileges option enabled.
• Users can access the dialog boxes listed above if they run a script with the Run script
with full access privileges option enabled.
• Users can access Layout mode and the Manage Scripts feature if the privilege set
assigned to their account permits it.
• All database files must have at least one active account or they can’t be opened. You can’t
use the Remove admin access from files permanently option if the accounts with Full
Access privilege sets are the only active accounts in the file. If you attempt to do so, you will
receive an error message.
• Consider the long-term needs of your users when defining access privileges. Communicate
their access privileges to them clearly in the About layout and follow the rules specified by
FileMaker. For more information, see
Documenting developer solutions (FileMaker Pro
Advanced).
Related topics
Binding files into a runtime solution (FileMaker Pro Advanced)
About creating runtime solutions (FileMaker Pro Advanced)
Displaying databases in Kiosk mode (FileMaker Pro Advanced)
Saving solution settings (FileMaker Pro Advanced)