Re: BackEnd Question

This may or may not help you, but I want to rant here <grin>

I have a philosophical problem with using security to keep people from
mucking around in a database. If actual data confidentiality is involved,
sure, add security. But just to keep people from doing something you've
told them not to do -- no. If they do something they've been told not to
do, you fire them. Simple as that.

It is generally accepted that men are not to go into the women's restroom
except under controlled conditions (ie janitorial staff). We don't make
people badge into the restrooms and refuse to open the door if they are not
of the appropriate gender. If we discover a man who habitually enters the
women's restroom, we fire him.

In short, I believe this is a management issue, not a security issue. If
users habitually use your software in unapproved ways, you warn them once,
then the discipline escalates by whatever policy your company follows. Of
course, you have to catch them

To do this, I would use an AutoExec macro which runs code that records the
user's name in a log table. This will catch all but the most determined.
My experience has been when you make people aware that they could face
disciplinary action, they stop mucking around.

Just my opinion.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L


"David W" <davidw@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23q5N2o0nFHA.3660@xxxxxxxxxxxxxxxxxxxxxxx
> I need a way to keep people from opening the backend database files except
> when they use the frontend.
> I have a split system that works fine, the database are connected via
mapped
> drive from each pc(no server software here).
> The issues is when someone opens the mapped drive from there pc, they can
> open the backend files and do whatever.
> I am going to ask a silly question<<<
> Are you supposed to make the backend a mde or is there something that I
> havent seen yet?
>
> Thanks for responding
> David W
>
>


.

Relevant Pages

  • Re: Is this possible??
    ... I understand Windows security but since I've not seen A2007 live, ... The backend is on the server in it's own file. ... database, but everyone does not need to have access to tblwage which is ...
    (microsoft.public.access.tablesdbdesign)
  • RE: Refreshlink error
    ... > User-level Security is redundant. ... to cover anyone using a different mdw to login to the database. ... maintain the backend. ... >> permissions to allow the default user and groups to change the design could ...
    (microsoft.public.access.modulesdaovba)
  • Re: setup
    ... Security is complex, and requires some study and practice to get it right. ... When you think you understand it, practice on a copy of your database. ... As for multiple users, you will want to split your database into frontend ... You put the backend on the server, and give each user a copy of the frontend ...
    (microsoft.public.access.security)
  • Re: READ ONLY ON NETWORK
    ... database into two components: frontend and backend. ... what you want to apply for security is called User Level ...
    (microsoft.public.access.queries)
  • Re: setting a password on a button on the switchboard
    ... Could you send me the sample database for the fourth option (4. ... > Security in an Access database can probably be broken down into two big ... > points about being easier than User Level Security, ... > What type of data are you trying to protect? ...
    (microsoft.public.access.forms)