Locking a Back end

  • Thread starter Thread starter Nick via AccessMonster.com
  • Start date Start date
N

Nick via AccessMonster.com

Hello all,

I have my BE on a shared network folder, and multiple FE's on client's
computers. I'm trying to secure the BE to the extent that your usual bored
worker won't get curious and accidentally delete something.

I have already restricted direct access to the BE, and what I want to do now
is let the FE be the only way to link to the BE data tables; i.e. I don't
want someone to be able to create a new database and link to the BE to change
it.

I am brand new to Access security and have read the Microsoft Security FAQ,
but it was a bit over my head. Is there a simple way to go about this, or a
tutorial anyone could point me to? Any help would be greatly appreciated.

Thanks,
Nick
 
Nick via AccessMonster.com said:
I have my BE on a shared network folder, and multiple FE's on client's
computers. I'm trying to secure the BE to the extent that your usual
bored
worker won't get curious and accidentally delete something.

I have already restricted direct access to the BE,
Click to expand...

How did you do this? If by windows security, be aware that all users need
create/read/write/delete permissions on the folder where the backend in
order to create the associated ldb file.
and what I want to do now
is let the FE be the only way to link to the BE data tables; i.e. I don't
want someone to be able to create a new database and link to the BE to
change
it.
Click to expand...

Since users need to link to the BE to use your FE, you really can't stop
them. You can do some simple things to keep most users out, but not the
determined.

Put the BE in a hidden share \\server\share$ rather than \\server\share
that will hide it in Windows Explorer, but if they know the path they can
find it. This will prevent them from linking to it.
You could create an autoexec macro that throws up a message (or not) and
then quits. This will prevent them from opening it directly. You would
also want to disable the shiftkey bypass in the backend.

Joan Wild
Microsoft Access MVP
 
Nick via AccessMonster.com said:
I am brand new to Access security and have read the Microsoft Security
FAQ,
but it was a bit over my head. Is there a simple way to go about this, or
a
tutorial anyone could point me to? Any help would be greatly appreciated.
Click to expand...
There really is no substitute for the FAQ but you might find the example on
my website useful. Try that and then re-read the FAQ. I cannot stress
enough the importance of working on copies of your files - it is *very* easy
for an inexperienced user to lock themselves out.

Good luck.
Keith.
www.keithwilby.com
 
The way I have denied direct access to the BE was just to put up a small form
that asks for a password on startup (I want the Administrator to be able to
access, but no other users). Incorrect password = Application.Quit

Like you said Joan, that's simple and won't keep out anyone determined, but I
am not terribly concerned about that - the Admin will keep a couple of copies
of the database (locally) that are backed-up weekly. The records in the
database are updated very slowly (engineering-related data), so what I am
usually looking at is about 1 or 2 inputs per week. Also, no outsiders will
have access to the application, and no insiders have any incentive to tamper
with anything.

Also, now that I think about it, I might put off the security for awhile to
see how necessary it will be. I am just building to specs, and security was
not mentioned at the time. I will ask the Admin what he thinks.

In the meantime, thanks for the help.

Nick
 
I secured my back end using the same mdw as I used for the front end. When a
user enters the front end, the tables are linked to the back end with no
problem. However, if a user tries to open the back end directly or tries to
link/import to/from the back end , they get the “You do not have the
necessary permissions .. “ message.
 
Wow, Keith, thanks for the advice about backing up DB's... I think it took me
about 5 minutes to lock myself out of my first one :P

Thanks to both you and Joan for the help and advice; I'm on my way to getting
the permissions correct.

Once again, thanks!

Nick
 
Wow, Keith, thanks for the advice about backing up DB's... I think it took
me
about 5 minutes to lock myself out of my first one :P
Click to expand...
No Problem Nick. You'd be suprised how many people choose to ignore that
advice! :o)
 
Back
Top