Database Security?

[RoseV]

Is there anyway to put a password on the database view of a program? I know you can set a password within Access when the database opens (user's view AND programmer's). But is there anyway to put a password JUST on the (Enter+Shift)?
I am creating a database for users that A) do not have a programmer in their group and B)have a little bit of Access knowledge (a dangerous thing...).

 

[Trevahaha]

Don't know if this is the best way, but maybe will work for you. You might want to disable SpecialKeys (which allows you to do the whole F11/Shift-Enter thing) and then create a button that has a "password protection" form that you create. This then would not utilize Access' Security, but instead use your own. Just create a form that either checks a table for a password or uses a static one in your code. Put a button on your form or create an AutoKey sequence which brings it up (like Ctrl-Shift-@ or something funky like that). If you enter the correct password:
AllowSpecialKeys = True

then just push F11.. there might even be VBA code that brings up the database menu, don't know.

Probably not the best, but it was quick to come to mind

Trevor

 

[RoseV]

Interesting! I'll look into that - it sounds feasible.
Thanks for the idea! I'll post back here with what I find works.

 

[danvlas]

"have a little bit of Access knowledge"

Then they may easily re-enable the Shift key by simply set AllowBypassKey property to True from outside ...

Sorry to spoil your joy, but it's better for you to know that.

HTH




Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[Trevahaha]

True true.

That's why it's always best to have security built in. However.. most people just rely on the fact that the end users are not going to go directly and edit data on the table level. I don't know of a way, even with Access security, to block this.

Trevor

 

[Trevahaha]

This would be accomplished, I think... by adding to the command line arguments: /cmd AllowBypassKey = True; ( i think)

RoseV - I think the only *really* secure way is to create a MDE file and then make changes to the MDB file and "post your changes" by replacing the MDE file each time. Sometimes more of a pain, but definitely the 'best' way to go.

Trevor

 

[danvlas]

With Access security:
Deny editing the tables for all users.
Base the forms on Select statements WithOwnerAccessOption.
User will not be able to edit the table unless through the form.

HTH




Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[RoseV]

Thank you guys for all your suggestions.

 

[JeremyNYC]

Trev,

There are some areas that are safe to speculate on. Security is not one of them. I understand that you're just trying to help, but because you don't have a very thorough understanding of Access security, you're putting Rose's database at risk.

==========

Rose,

Get, read, re-read, and then read again the MS Access security FAQ. BACK UP your database before you do anything with security. Secure your database. Then disable the bypass key, leaving yourself a way to re-enable it from a form. MAKE SURE you back up your database along the way.

Do not attempt to make your own security. It will not be as secure as what is built in to Access, it will not have as many features, and it will not have a userbase sufficient to answer your questions about it.

The security FAQ is on the MS site, and there's a copy on my site.

Jeremy

==
Jeremy Wallace
AlphaBet City Dataworks

http://www.ABCDataworks.com

Access Databases for Non-Profit Organizations

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.

 

[Trevahaha]

Jeremy -

I completely understand and agree. I was feeling that he wanted a work around w/o MS Access Security. I wasn't sure how security was needed - there is never a substitute for this. I was assuming it was a low-risk situation.

Trevor