Protect Front and Backends

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

Guest

In all honesty, I could care less that people look at the frontend. It is
the backend where all the data is stored that you should really need to
protect.

How do I protect a backend?
How do I keep someone from just deleting the backend from a drive?
How do I keep someone from looking at the data that is there?

Just had that thought while I am pouring through the front-end security.
 
Hi.
How do I protect a backend?
Click to expand...

One protects the back end with user-level security. Many developers find it
easiest to develop the entire application as a single file and then when
it's finished, the database file is split into a front end and back end.
How do I keep someone from just deleting the backend from a drive?
Click to expand...

Take away his keyboard and mouse. Seriously though, one can't completely
prevent this, merely make it more difficult to do so. All users in a
multiuser database must have "Full Control" permissions of the database
files. Make sure that backups are made frequently enough so that this type
of accident will not become a disaster. One can make it more difficult to
delete the database file accidently by giving the users shortcuts to launch
the database application, placing the database on a hidden network shared
directory, and removing the ability for users to map directly to the network
shared directory.
How do I keep someone from looking at the data that is there?
Click to expand...

User-level security can be adequate for many situations. However, someone
determined enough to break through this security can do so.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Gunny given some great advice here...I can't really add anything more.

However, the main problem at the end of the day is that the back file is
just that, a simple file.

that file can be deleted, or take away by one of your employees, and their
is not much you can do.

Your employees can take and delete a word document. The same applies to
excel, or to ms-access.

If you need a secure system, then you can use the other database engine on
the office cd. This means you essentially use sql server.
There is a free copy of the desktop edition of sql server on every office cd
for use with ms-access.

If you use sql server for your data, then employees etc can be prevented
from deleting the files, or even every seeing the files.

So, if you want a secure system, then you can continue to use ms-access, but
the back end data part would have to be put on a server base system (like
sql server).

So, ms-access can work both in a file based system, and a server based
system. When you use ms-access in a file based system, you can't make any
real claims of security here..as there is very little.
 
Back
Top