Database Reference
In-Depth Information
You're done setting up File Access for the Access file.
In a closed system (one where several FileMaker databases work together), you may want to
authorize other files in the protected database. Or another file (or set of files) may need its
own list of authorized files. You don't have to authorize all the files in a system with one an-
other, though. As with the rest of your security settings, take the pessimistic approach and
authorize only the files that specifically need access to protected databases. You can always
add more access later.
To test the Invoice database's File Access settings, close it and make sure all its windows are
closed. If you open a protected database with a [Full Access] account and then leave it open
on your computer, another user could sneak into your office while you're away and authorize
a file without knowing the proper account information. So if your databases contain sensitive
data, take all normal precautions: Close files when you leave your office, lock your door, and
so on. And make sure protected files are closed when you're testing access.
Figure 18-19. When a file is protected from external access, unauthorized files can't be used to
sneak into a file. Without this protection, anyone with access privileges to a file can sneak around
older privileges to create external references and use design functions, like
ValueListItems()
or
ScriptNames()
, to get metadata about your database.
Now open a nonauthorized file (use the No Access sample file: Account Name and Password
are both “noaccess”) and try to create a table occurrence from Invoices Security on No Ac-
cess's Relationships graph. You see the standard login dialog box. The only way out of the
Specify Table dialog box is to click Cancel or to enter a [Full Access] account name and
password. If you enter valid information for an account that doesn't have full access, you'll
see a warning like the one in
Figure 18-20
.
