User manual

176 | Protecting databases with accounts and privilege sets
1 Outputting data. Prevent users from printing or exporting data.
1 Menu access. Make only a limited set of menu commands available.
You restrict what users do in a file by requiring them to enter an account name
and password when they attempt to open a file. The account name and
password they enter determines which privilege set will be used and the
privilege set limits what they can do in a file. For more information about
accounts and privilege sets, see the following section.
You can define privileges in a shared file while clients are using it. Any
privilege changes that affect a current client do not take effect until the client
closes and reopens the file.
The privileges that you set up apply to a single file only and all database tables
within that file. If your database solution consists of multiple files that you want
to protect, you may want to combine all of these files into one multi-table file.
Then you can define privileges in only a single file to manage access to the
entire database solution. If you don’t want to combine the files into one file,
then you should define privileges in each file that contains items you want to
protect.
Important If you create a relationship in one file that references a table in another
file, you cannot manage access privileges for the related table in the first file. The
privileges defined in the other file control access to that table.
Accounts, privilege sets, and extended privileges
Accounts authenticate users who are attempting to open a protected file. Each
account specifies an account name and usually a password. Any user that
cannot specify valid account information won’t be able to open a protected file.
Each database file contains two predefined accounts: Admin and Guest. For
more information, see
“About the predefined accounts” on page 179.
φμπ10_υσερσ_γυιδε.βοοκ Παγε 176 Μονδαψ, Αυγυστ 25, 2008 3:59 ΠΜ