Once you’ve established each user's access level, you set up a privilege scheme for each table. A DBF table’s privilege scheme controls three things:

Which group can access the table. (The user’s group name is matched with the table’s group name to allow table access.)

Which user access levels can read, update, extend and/or delete the table (table privileges).

Which user access levels can modify and/or view each field within the table (field privileges).

After a user logs in, dBASE Plus determines what access the user has to that DBF table and its fields by matching the user’s access level with the rights you specified in the table’s privilege scheme.

For example, if you assigned a user an access level of 2, that user’s access to the table, and to various fields within the table, are determined by the privileges you assigned to Level 2 in the table privilege scheme.

In building a table privilege scheme, note the following:

A user’s ability to access a table is a function of both the access level of the group and the user’s individual access level. However, only the user’s access level determines what the user can do with a table once it is opened.

If you do not create a privilege scheme for a table, all users of the group can read and write to all fields in the table.

Access rights cannot override a read-only attribute established for the table at the operating system level.