I have a 2K database with a front end linked to a back end. I need to lock
down or secure both ends so a user can not access the raw data in tables
etc. I also need usernames and passwords for 50+ users. I've experimented
with securing the database but can't get it the way I want it. I can still
use the shift key to obtain access. Anyone have a link to a site or
something to give me a guideline as to what I can do?

Thanks

You need Jamie's Software - Access Property Editor.

Download from http://www.jamiessoftware.tk/

On Fri, 20 Jan 2006 12:55:10 GMT, "Brad P" <bradp_xx@hotmail.com>
wrote:

Well, Access security is better than that. But you'll have to
download, study, and fully understand MSFT's security FAQ before
proceeding.
Yet this Access security can be cracked. If you really need strong
security, Access is not the best platform. But then you already knew
that, because you did your research *before* you started.

-Tom.

[color=blue]
>I have a 2K database with a front end linked to a back end. I need to lock
>down or secure both ends so a user can not access the raw data in tables
>etc. I also need usernames and passwords for 50+ users. I've experimented
>with securing the database but can't get it the way I want it. I can still
>use the shift key to obtain access. Anyone have a link to a site or
>something to give me a guideline as to what I can do?
>
>Thanks
>[/color]

I just need to prevent the average user from getting into the backend of my
application. My application doesn't contain critical data. The previous post
with APE may be my ticket. Thanks for that!

"Tom van Stiphout" <no.spam.tom7744@cox.net> wrote in message
news:hct1t1580rvovr53v2a3qspvfdfae2qve6@4ax.com...[color=blue]
> On Fri, 20 Jan 2006 12:55:10 GMT, "Brad P" <bradp_xx@hotmail.com>
> wrote:
>
> Well, Access security is better than that. But you'll have to
> download, study, and fully understand MSFT's security FAQ before
> proceeding.
> Yet this Access security can be cracked. If you really need strong
> security, Access is not the best platform. But then you already knew
> that, because you did your research *before* you started.
>
> -Tom.
>
>[color=green]
> >I have a 2K database with a front end linked to a back end. I need to[/color][/color]
lock[color=blue][color=green]
> >down or secure both ends so a user can not access the raw data in tables
> >etc. I also need usernames and passwords for 50+ users. I've experimented
> >with securing the database but can't get it the way I want it. I can[/color][/color]
still[color=blue][color=green]
> >use the shift key to obtain access. Anyone have a link to a site or
> >something to give me a guideline as to what I can do?
> >
> >Thanks
> >[/color]
>[/color]

Actually, to keep my users out of the back end, and front end code/forms
etc, you don't need any security..or even any code for that matter.

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. And, if you deploy a mde..then things are well locked up.

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/AlbertKal...s/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/AlbertKal.../msaccess.html

For the back end...I just put in a autoexec macro..and tha keeps them
out...I use:

So, I make a macro called AutoExec. In the macro, I put the following code:

Action Parms
Msgbox message:You do not have permissions to run this file
Beep: Yes
Type: Critical
Title: Can not run

Quit: Options:Exit

As an alterative, you an make a nice little form in the back end, and set
the startup options to run that form that displays a message, and then when
they click ok...you do a application.quit. Eithway..this keep 99% of the
users out..as they think they don't have persmissions...


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.members.shaw.ca/AlbertKallal