Limit access to back end of database on server computer

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

Guest

I have created a database, which I have split into a back end and front end.
The back end is located on a server computer that was purchased for our
project. I could not get the front end of the database to work without the
person having access to the folder where the back end is located. This means
that everyone will have access to the back end file, and be able to make
changes.
Our Quality Assurance people have an issue with this.
Is there any way to make it so that people cannot make changes to the format
of the back end (such as deleting a column) while still allowing them to
enter data from the front end on their computer? I've set them up with mde
files for the front end, so they cannot change it from there.
Thanks,
Lanee
 
I usually setup a autoexec maco in the back end.

if a user tries to open the back end, the macro gives them a message that
they don't have permissions, and when they click ok..the database closes.


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.

And, to disable the "shift key", simply grab my shift key utility here to
turn off the shift key by-pass

http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

The above is not perffect, but it keeps 99% of average users out....
 
yeah.. if you used 'Access Data Projects' then you can easily prevent
people from getting to your server
 
Ok, I'm pretty new to this, but I figured out how to do that. If I save this
macro, does everybody (including me) no longer have access to the back end on
the server computer?

If so, that means if I need to make changes for any reason, I have to do it
on a backup version I have on my computer, then replace the version on the
server. Is that correct?

Thanks for the help
 
Well, to normally by-pass your start-up form, or autoexec macro, you hold
down the shift key during startup.......


So, that will get you in....

In fact, you really can't develp your front end any other way either....


You read the follwing re-post of mine about the front end part, and you
should also consider locking the front end part also...


===============

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

Of course, during development, you will hold down the shift key so your
startup settings don't run. You then develop for awhile, and then to test in
"user" mode, you exit..and then re-enter the application without the shift
key bypassed. You will likely do this dance all day long as you run/test as
user mode, and then flip back in to developer mode (shift key used..so you
don't get the main custom menu). So, you can't develop, or really modify
things when you run your application with the startup settings...so you must
shift-by-pass them when you want to work.

And, in fact, I use alt-f4 to exit the application...the mdb file should
still be highlighted in the windows explore..so, then you hit enter key
(and, hold down shift key if you need be). This key stroke sequence and
exiting and re-entering the application will occur CONSTANTLY all day long
when you are developing.

When you finally have things just right...you create the mde
you plan to distribute, and place that on each pc....
 
Lanee said:
I have created a database, which I have split into a back end and
front end. The back end is located on a server computer that was
purchased for our project. I could not get the front end of the
database to work without the person having access to the folder where
the back end is located. This means that everyone will have access
to the back end file, and be able to make changes.
Our Quality Assurance people have an issue with this.
Is there any way to make it so that people cannot make changes to the
format of the back end (such as deleting a column) while still
allowing them to enter data from the front end on their computer?
I've set them up with mde files for the front end, so they cannot
change it from there.
Thanks,
Lanee
Click to expand...

Albert suggested what is likely the best solution for your needs. If
you need more security, that is keep them out even if they know how to press
the shift key you can check out Access User Level Security.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can easily lock
you out of your database, which might require the paid services of a
professional to help you get back in.

Practice on some copies to make sure you know what you are doing.

Access 2007 as it doesn't support user-level security.
 
Back
Top