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

Chapter 19. Linking Access Front-Ends to... > Password-Protecting Access Front-End...

Password-Protecting Access Front-Ends

All production database applications should have at least some level of security applied. The minimum level of security is password-protecting the front end .mdb file. The problem with password protection is that users can open any Access object—except password-protected VBA code—in Design view and make changes to the front end. The only method of preventing unauthorized design changes to a password-protected .mdb file is to distribute the front end as an .mde file or supply a runtime version of your application, which requires the Access 2003 Developer Extensions’ runtime version of MSAccess.exe, which was included with the Microsoft Office Developer Edition (MOD) for earlier Office versions. Creating an .mde version from a copy of your front-end .mdb file or use of runtime Access prevents users from opening any object in Design view. As a general rule, don’t password-protect or create .mde versions of back-end .mdb files. Instead, use share- and file-level security, as described in the earlier “Establishing Network Share and File Security for the Back End” section, apply user-level security, or both.

→ For more information about user-level security, see “Applying User-Level Security to Access Front-Ends,” p. 783.



PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


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