Chapter 7
|
Using the Developer Utilities 73
Removing full access privileges
from databases
FileMaker Pro and FileMaker Pro Advanced use accounts, privilege
sets, and extended privileges to protect FileMaker databases. You can
use the Developer Utilities to remove all administrative accounts from
a file. For more information about accounts and privileges, see Help.
Use the Developer Utilities to prevent users from altering the design
and structure of your database files and from changing any accounts
or privileges that you’ve set up. If you enable the
Remove admin access
from files permanently
option:
1 Users can’t access these dialog boxes: Define Database, Define
File References, Define Custom Functions, and most of Define
Accounts & Privileges.
1 The text version of custom functions is removed.
1 Users can access the Extended Privileges tab in Define Accounts &
Privileges if their account has the Manage extended privileges option
enabled.
1 Users can access the dialog boxes listed above if they run a script
with the Run script with full access privileges option enabled.
1 Users can access Layout mode and ScriptMaker if the privilege set
assigned to their account permits it.
Note 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.
Important Selecting this option permanently deletes from the database
all accounts that were using the Full Access privilege set. This will
permanently eliminate access to Layout mode and ScriptMaker, and
all Define dialog boxes, except for the Extended Privileges tab of the
Accounts & Privileges dialog box, for all database files in the
solution, whether they’re opened in a runtime application, in
FileMaker
Pro, or in FileMaker Pro Advanced. Structural and design
elements of the files cannot be 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.
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
“Creating an About layout” on page 79.
