How to password protect Access code

[Tony Girgenti]

Hello.

How do give a customer an MDB file to use but password protect the code and database window to protect everything except it's intended use ?

Any other tips/ideas concerning this subject would also be appreciated.

Thanks,
Tony

 

[Albert D.Kallal]

You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you
do not have to bother setting up security.

Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.

Check out:

http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

Of course, the last thing you need to do before you deploy is to create mde
file. This removes all code and prevents users from modifying it (the "e" in
the mde stands for executable). I talk about this issue here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Br@dley]

Hello.

How do give a customer an MDB file to use but password protect the
code and database window to protect everything except it's intended
use ?

Any other tips/ideas concerning this subject would also be
appreciated.

Thanks,
Tony

Why not give them an MDE version of the database? That way all
object/code design is physically removed making it inaccessible (and it
will probably run a bit faster too).

Otherwise you'd need to implement workgroup security and set permissions
on the database objects (including modules for Access97 and earlier).
For Access2000 onwards you need to set a seperate password for the VBA
code.

I'd go the MDE route. I think in Access2005 they are removing workgroup
security as it's becoming mostly redundant with the use of MDEs (except
for data permissions IMO)???

To create an MDE copy of your database go to Tools/Database
Utilities/Make MDE file (may differ in diff versions).
Note: you must keep an MDB version as your development copy. When you
make changes to it simply create a new MDE to distribute to clients.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response