Help

Protecting databases
F
ILEMAKER PRO HELP 466
• Editing extended privileges for a privilege set
• Editing other privileges
11. When you’ve finished editing this privilege set, click OK.
12. In the Manage Security dialog box, do one of the following:
• If you’ve finished working with accounts and privileges, click OK. In the dialog box that
appears, enter an account name and password that is assigned the Full Access
privilege set, and click OK.
• To assign the privilege set to one or more accounts, see Creating accounts or Editing
existing accounts.
Notes
• In the Custom Record Privileges and Custom Field Privileges dialog boxes, you can change
the order of tables or fields in the list by clicking one of the column headings. To switch
between
ascending and descending order, click the column heading again.
• If you prohibit creating records in a file or table, then duplicating records is prohibited as
well.
• Users that cannot view certain records can still browse these records, but the user will see
<No Access>
instead of the field data within each record.
• Many features in FileMaker Pro are affected when you limit access to records, fields, and
tables within a file. The following table summarizes the effects for some features.
Feature Effect of limiting data access
Lookups and
Relookups
Lookups and relookups are defined by three components, all of which can be
affected by data access privileges:
• At a minimum, the match fields used in the relationship must have view
privileges. Also, no lookup will occur for any records that are not
viewable in both the source and destination tables because a match
cannot occur under these circumstances. This includes the first related
matching record, as well as any records used to copy the next higher or
lower value.
• At a minimum, the source field for the lookup must have view privileges.
• The destination field for the lookup must have edit privileges.
FileMaker Pro does not display an error message if a lookup operation skips
certain records due to access privilege restrictions.
Accessing related
data
At a minimum, both matching fields in a relationship must have view
privileges in order for the relationship to work. Any
related fields you want to
display based on the matching fields must also have view privileges at a
minimum.
Finds The found set is always filtered to display only those records that have view
privileges at a minimum. The results of the Get(FoundCount) function are
also affected if access is limited.
Value lists When a value list is based on the content of a field, and view privileges are
prohibited on the field, then the value list does not display any values. This is
so that users do not inadvertently gain access to confidential information.
The results of the
ValueListItems function are also hidden when access
is limited.