Securing a database

[Guest]

I developed a database for a company out of state that I thought would be a
one-time development. Now, a company in another state wants to use it.

I want to secure the production database so that the clients do not have
access to my queries, forms, reports and macros. Since both of these
companies are out of state, I don't have access to their LAN, so I can't
easily deploy the database using the Access Security Wizard. Is there
another way to secure the database the way I would like? By the way, the
tables are in a separate database on their server.

Thank you for your help.

John

 

[Joan Wild]

I want to secure the production database so that the clients do not have
access to my queries, forms, reports and macros. Since both of these
companies are out of state, I don't have access to their LAN, so I can't
easily deploy the database using the Access Security Wizard. Is there
another way to secure the database the way I would like? By the way, the
tables are in a separate database on their server.

You can secure it such that they don't have to login. See
www.jmwild.com/SecureNoLogin.htm

Just be aware that if they are determined, they can break Access Security.
There is no desktop database program that is completely secure.

 

[Guest]

Joan,

Thank you for your reply. I have another question.

I went through your "Access 2002/2003 Security Step by Step" and it was very
informative. When I open the database this way, a user still can see all of
my query structures even though they can't modify them. How do I restrict
access completely? Is a runtime version the only way?

Thanks.

 

[Joan Wild]

Joan,

Thank you for your reply. I have another question.

I went through your "Access 2002/2003 Security Step by Step" and it was
very
informative. When I open the database this way, a user still can see all
of
my query structures even though they can't modify them. How do I restrict
access completely? Is a runtime version the only way?

There are a number of things you can do:

Backup your database; you can easily lock yourself out playing around with
these features.

Create custom menus/toolbars for use throughout your application.
Create a startup form (a main menu form if you have one) that is opened on
startup.
Use the features in Tools, Startup to
set the startup form
set your default menu (the custom one you made)
disable all the checkboxes about allowing built in menus, toolbars,
changes, all special keys (this will disable the F11 key, among others)
hide the db window (ensure the custom menu you create does not
include the Windows, Unhide item)

If you need to bypass these startup features, you can hold the shift key
down while you open the db. If you feel that your users may use this to
bypass your settings, you can disable the shift key bypass - there's an
example in help for doing this(look for AllowBypassKey) or at
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm

You can also create a MDE from your database, which will prevent changes to
forms, reports and modules (If you do this, be certain to keep your original
mdb in case you need to make changes).