Security on a Database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I work independently but I am currently buiding a database to capture staff
exit interviews for a Corporate Client. I am a bit of a novice in ACCESS but
have been able to build queries and forms to meet all the needs of the
program.

Whilst I built it for myself, to be able to calculate patterns and trends of
dissatisfaction among staff - they (The Client) have requested to view all
the interviews which can be viewed from a form which has about 10 page tabs.

Rather than send them the main table which the form points to, I would
prefer to send them the database but only allow them to view one form within
it.

Can someone help me with :
a: How I program the database to secure everything else from being viewed
excpet this form. The form already has open on activate database built into
it but I want to be able to prevent them from going anywhere else.

b: How can I package up the database so that I can send it across to them
and of course they would require to have ACCESS on their site.

Hope someone can help. Many Thanks!
Angeline
 
The security topic is not small, I suggest you read the help file, but just
to point you where to start:

a. Use the "User-Level Security Wizard" located in Tools/Security menu.

and for
b. If you your client has Access, simply send the database, security file,
and a shortcut (the security topics in Access help have more detail) in a CD
or via e-mail in a zipped file, if the client does not have access and you
want to distribute more applications in the future, I will recommend you buy
the Developer extensions for Microsoft office if you are using Access 2003,
they have a packaging wizard that helps distribute applications with their
own setup,
 
Thank you very much. Yes, upon reading some of these threads I realised that
security is not so simple. I will do as you've suggested and thank you very
much for your response.

:)
Angeline
 
in message:
Thanks Jeff, I appreciate the warning and will follow your advice.
Click to expand...

You're welcome, good luck with your project.
Post back into this group if you run into any problems.
 
in message:
Thank you. You can count on that!

This forum is just so helpful thanks to people like you ;)
Click to expand...

Thanks Angeline, that was very nice of you to say.
I enjoy helping people.
:-)
 
Angeline said:
Rather than send them the main table which the form points to, I would
prefer to send them the database but only allow them to view one form
within
it.

Can someone help me with :
a: How I program the database to secure everything else from being viewed
excpet this form. The form already has open on activate database built
into
it but I want to be able to prevent them from going anywhere else.
Click to expand...

You could just make a copy of it, and strip out all the other forms/reports.

If you go with security, since you need only one group, you can secure it
such that you don't have to send them the workgroup file, and they can use
their default system.mdw - More details at www.jmwild.com/AccessSecurity.htm
There is also a lot you can do to lock down the interface and keep the
curious out.
If you're just looking to keep the idle curious out, there are a number of
things you can do:

Create custom menus/toolbars for use throughout your application.
Use the features in Tools, Startup to
set your default menu (the custom one you made)
disable all the checkboxes about allowing built in menus, toolbars,
changes etc.
hide the db window (ensure the custom menu you create does not
include the Windows, Unhide item
Click on the Advanced button and uncheck the allow special keys
(this will disable the F11 key, among others)

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).

Again I wonder if it's really worth it? Just send them a stripped down
mdb.
b: How can I package up the database so that I can send it across to them
and of course they would require to have ACCESS on their site.
Click to expand...

You just need to attach it to an email - perhaps zip it first.
 
Back
Top