MSAccess Security

[VAL]

I just saw a dtb that does exactly what I want but I don't know how they did
it. I have a multiuser dtb and need to hide all of Access's commands. I
have put in security where each user has their own password and I have an
admin password with all priviledges. They are restricted to view/input but
the menus are still there and they try anything...

Thank you in advance for your help. Please be precise, step by step. I am
very new at this and have received helped from a programmer who unfortunately
is no longer available.

Val

 

[Rick Brandt]

I just saw a dtb that does exactly what I want but I don't know how
they did it. I have a multiuser dtb and need to hide all of Access's
commands. I have put in security where each user has their own
password and I have an admin password with all priviledges. They are
restricted to view/input but the menus are still there and they try
anything...

Thank you in advance for your help. Please be precise, step by step.
I am very new at this and have received helped from a programmer who
unfortunately is no longer available.

Val

Tools - Startup has all of the options for disabling the built in Access
interfaces.

 

[VAL]

Yes, I know about Tools, startup - thank you. But what prevents the users to
do the same and make the menu reappear? I need something that disabled
Access to the users passwords but not the admin. It also needs to be for
that database only as if I do it to Access, when the students (I work for a
school and the database is for the teachers - PC's are used by both) go into
Access, the menus are then gone.

 

[Keith W]

Yes, I know about Tools, startup - thank you. But what prevents the users
to
do the same and make the menu reappear? I need something that disabled
Access to the users passwords but not the admin. It also needs to be for
that database only as if I do it to Access, when the students (I work for
a
school and the database is for the teachers - PC's are used by both) go
into
Access, the menus are then gone.

Implementing User Level Security (ULS) at "getting started" level will
require hours of research and some trial and error on dummy db files. If
you want to take this route then start with the MS FAQ on ULS. It is all
killer, no filler so you need to understand it all. There's a link to it on
my web site along with my step-by-step example.

You'd also need to provide custome menus (removing the built-in ones) and
disable the bypass (shift) key.

Good luck.
Keith.
www.keithwilby.com

 

[Rick Brandt]

Yes, I know about Tools, startup - thank you. But what prevents the
users to do the same and make the menu reappear? I need something
that disabled Access to the users passwords but not the admin. It
also needs to be for that database only as if I do it to Access, when
the students (I work for a school and the database is for the
teachers - PC's are used by both) go into Access, the menus are then
gone.

They will not have access to the Startup properties unless they know to hold the
shift key down while opening the file to "Bypass" those settings. If you are
worried about that you can disable that feature as well. Then you only have to
worry about people who know how to re-enable that.

If you have put in your own security scheme rather than using the built in User
Level Security that comes with Access then I'm afraid that your efforts have
been a huge waste of time if your intent was to erect barriers to people who
know how Access works.

Such strategies are fine for "clerical staff", and that type of user is unlikely
to know about holding the shift key down to suppress the Startup settings. If
you need to have security that works with more Access-savvy users then you
really need to implement full blown Access security. That too can be hacked,
but it does require some external tools and a higher level of "motivation" to do
so.

With User Level Security implemented you can disable the bypass key in a manner
that can only be reversed by a user account that has administer authority on the
database.

 

[VAL]

Thank you. I am quite willing to go that route and all my menus are custom
built (events to exit, go back, etc.) - I also have a custom made toolbar for
the users that has all they need...

What is MS FAQ on ULS? Sorry just not familiar with these abbreviation and
it's my second time using this post method. Also where is your website?
Would really need those my step-by-step examples.

Thanks again for your prompt response.

 

[Keith W]

Thank you. I am quite willing to go that route and all my menus are
custom
built (events to exit, go back, etc.) - I also have a custom made toolbar
for
the users that has all they need...

What is MS FAQ on ULS? Sorry just not familiar with these abbreviation
and
it's my second time using this post method.

Microsoft Frequently Asked Questions.

Also where is your website?
Would really need those my step-by-step examples.

www.keithwilby.com (from my sig line) )

 

[Albert D.Kallal]

Yes, I know about Tools, startup - thank you. But what prevents the users
to
do the same and make the menu reappear?

You should be distributing a mde to those uses, and thus they can't change
the forms anyway. Further, if you lock out the shift key by-pass, then they
can't get to your menus anyway.

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