MDE

  • Thread starter Thread starter paul wheeler
  • Start date Start date
P

paul wheeler

can anyone advise me on the benefit of creating and MDE
file. The reason i ask is because i want to stop people
having access to any other part of MS Access to play
around with the form, table, queries and reports, but i
still want to be able to access them....

Paul
 
Your Access database contains 2 versions of the code in modules (including
the modules of forms and reports):
- the text version - what you seen and edit, and
- the compiled version - machine-type code that actually runs.

When you create an MDE file through:
Tools | Database Utilities | Make MDE
Access creates another copy of the database with the same name and an MDE
extension. This MDE file contains *only* the compiled version of the code,
i.e. the text version is absent. This means there is *no* way for a curious
user to read or change your code: the text is just not there to change. It
also means the database cannot decompile. And design mode is disabled for
forms, reports, and modules.

The user can still modify the tables and queries though. Often you need
little more than to make the settings under:
Tools | Startup
so that the database is not shown at startup, and special keys are disabled.
For something more, set the AllowBypassKey, and create your own menus,
toolbars, shortcut menus. That's a basic padlock that's adequate for the
non-malicious nosy user.

If you need a stronger padlock, you can create an MDW file and set up
security levels in Access. You can also encrypt the file if necessary.

If you need a safe rather than a padlock, don't use Access.
 
Back
Top