• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 30. Securing Your Database > Securing a Desktop Database

Securing a Desktop Database

If you explore any of the main editing forms in the Housing Reservations (Housing.mdb) database (for example, frmEmployees, frmDepartments, and frmFacilities), you’ll discover code in each form’s Load and Current event procedures that enables and disables various controls and features on the form depending on the sign-on status of the user. Also, when you start the application by opening the frmSplash form, a sign-on form opens and asks you to identify yourself and enter a password. Users of the application can be application administrators, department managers, or employees, and the code controls the actions that each different type of user can perform.

These measures might keep the casual user locked out of features they shouldn’t be allowed to use, but they don’t prevent anyone who has a retail copy of Access from opening the database and then rummaging around in the code to figure out how to break through this security. If you really want to prevent unauthorized access to the objects in this database, you must implement the security features built into Access.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint