Secure Access 2002 App for dissemination by CD

[Mark Page]

I could do with a little help.

I've built an Access 2002 application which I wish to
supply completely secure to my customer.

I'm aware of the conversion to an MDE file, but this
leaves the tables, queries etc visible and still able to
be edited.

I've also read the knowledge base articles 305542
(Understanding the role of workgroup Information files in
Access security), and 289885 (Overview of how to secure a
Microsoft Access Database) both of which are for Access
2002.

My aim is to supply the application (on a CD) with a MDW
file that is only called upon when my application is used.
In other words when the customer uses Access for his own
purposes he will have Access open unsecured for his
application.

Ideally what I would like to have is the application open
(without a password) to all users, but all users excluded
from seeing code, queries and its construction.

I have also down loaded the FAQ's (SecFaq.exe) which I
notice are only for up to Access 2000.

I blithely started out using the above FAQ's, and
carefully recording what I did on paper. However, I am now
prompted to provide a password at log on (although I
haven't set one). I OK the dialog box and I get into
Access. As this is not quite what I expected I am loth to
go on in case there is a fundamental difference between
the above knowledge base articles the FAQ's and I may
secure myself out of Access.

If someone could offer some advice, or refer me to an
article that addresses my problem I'd be very grateful.

Sorry I've been a bit long winded. It's a Scottish trait...

Thanks

Mark

 

[Joan Wild]

I could do with a little help.

I've built an Access 2002 application which I wish to
supply completely secure to my customer.

First thing you need to understand is that you can never completely secure
an Access database. A determined person can break your security.

I'm aware of the conversion to an MDE file, but this
leaves the tables, queries etc visible and still able to
be edited.

You can use the settings in Tools, Startup to hide the database window,
limit menus/toolbars, etc. You should create custom menubars/toolbars for
your application, so that users can't get into things they shouldn't.

I've also read the knowledge base articles 305542
(Understanding the role of workgroup Information files in
Access security), and 289885 (Overview of how to secure a
Microsoft Access Database) both of which are for Access
2002.

My aim is to supply the application (on a CD) with a MDW
file that is only called upon when my application is used.
In other words when the customer uses Access for his own
purposes he will have Access open unsecured for his
application.

You should supply them with a desktop shortcut that utilizes the wrkgrp
switch to specify the secure mdw to use. The target would look like
"path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw"

They'd use this shortcut to start your application, and for all other Access
sessions they'd use the default system.mdw on their computer.

Ideally what I would like to have is the application open
(without a password) to all users, but all users excluded
from seeing code, queries and its construction.

It is possible to secure a mdb and not require a login, as long as you only
need two levels of security (you as developer, and everyone else). If you
want details, post back.

I have also down loaded the FAQ's (SecFaq.exe) which I
notice are only for up to Access 2000.

It applies to 2002 as well.

I blithely started out using the above FAQ's, and
carefully recording what I did on paper. However, I am now
prompted to provide a password at log on (although I
haven't set one). I OK the dialog box and I get into
Access. As this is not quite what I expected I am loth to
go on in case there is a fundamental difference between
the above knowledge base articles the FAQ's and I may
secure myself out of Access.

When you created a new workgroup file, Access made it the default one to
use. You can use Tools, Security, Workgroup Administrator to set system.mdw
as the default. Create a desktop shortcut as outlined above, for your
secure database.

If someone could offer some advice, or refer me to an
article that addresses my problem I'd be very grateful.

Security Whitepaper
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q148555

Although the whitepaper is old, it contains information to help you
understand security.

Other good reads
Lynn Trapp's
http://www.ltcomputerdesigns.com/Security.htm

Jack MacDonald's
www.geocities.com/jacksonmacd