How Will this Chapter Help Me?


Once again, I am going to provide separate overviews: one for the database administrator (DBA) and the developer and one for the IT manager. I do this because people in each of these categories will approach the chapter in a different way. The DBA and the developer need to understand how to change the database options (as shown in Figure 3-1) and attributes and what effect those changes will have on their databases. On the other hand, the IT manager should be aware of how changes to those options and attributes might affect databases that are important to his or her company's business.


Figure 3-1: Choose the database options from the Tools menu.

Overview for the Database Administrator and the Developer

This chapter illustrates the database options most pertinent to a DBA or developer who is trying to protect an Access database. The DBA and the developer should be aware that any user who can choose Options from the Tools menu can change all these settings manually. In situations where the number of users is small, manually reviewing the options on each workstation is possible. For larger groups of users and databases where some management issues are being encountered , I recommend that you enforce these security- related options by using VBA code for when users open the database. Finally, you should consider hiding the important tables, queries, forms, and modules by using the manual process demonstrated. You should also consider using VBA code techniques to hide objects and even add the system tables attribute to a normal table so that it is visible only when a user chooses the Show Systems Table option.

Issues with the Compact on Close option will not only cause security problems but will also confuse users who come across the discarded databases that failed the compacting process. Do not use this option for important databases unless you monitor for failed compactions.

Overview for the IT Manager

Even if you don't add any other security to your database, you should review your databases with your DBA or developer and determine whether there are objects that you should hide from your users. This method isn't foolproof, but, coupled with setting the startup options, it will foil users who occasionally like to snoop around your database. No actions that a developer can take here cannot be undone by another developer or DBA, however. In other words, these changes are not at all foolproof but simply act as a deterrent to those small-time mischief- makers .




Real World Microsoft Access Database Protection and Security
Real World Microsoft Access Database Protection and Security
ISBN: 1590591267
EAN: 2147483647
Year: 2003
Pages: 176

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net