Re: Change data on Form and NOT on Table
From: Ricardo (ricardo.ferreira_at_bentley.co.uk)
Date: 08/11/04
- Next message: Bob: "I will Pay for a Invoice/Statement template"
- Previous message: M.L. Sco Scofield: "Re: =Date()"
- In reply to: Joan Wild: "Re: Change data on Form and NOT on Table"
- Next in thread: Joan Wild: "Re: Change data on Form and NOT on Table"
- Reply: Joan Wild: "Re: Change data on Form and NOT on Table"
- Messages sorted by: [ date ] [ thread ]
Date: 11 Aug 2004 01:18:10 -0700
Joan
Thanks, your website was really helpful.
I now have a better understanding of MS Access security.
I still have some questions though:
1) How to make sure that the members of a group can only change data
on the forms and not on the tables?
In User Group Permissions:
In order to tick the Add, Mod, Del boxes in Forms; I have to tick them
in Tables as well.
2) How to make sure that the shortcut with the /wrkgrp option is the
only way to open the database? Otherwise, one can always log in
through System.mdw and have Admin permissions.
3) This database is going to be deployed on a PC outside my network.
Will I have to rebuild the MDW file and set the permissions all over
again, or is it enough to copy the MDW file as well as the shortcut?
Thanks,
Ricardo Ferreira
"Joan Wild" <jwild@nospamtyenet.com> wrote in message news:<uYoDaehfEHA.2916@TK2MSFTNGP12.phx.gbl>...
> Ricardo wrote:
> > Hi
> >
> > Is it possible to deny all users -- except the Admin -- of opening an
> > MS Access "database" in design mode (SHIFT+ENTER)?
> > I created the user USER belonging to the group USERS, but when I try
> > different combinations of permissions it doesn't do what I expect it
> > to.
>
> You need to download and study the security FAQ. You shouldn't apply
> permissions to any user in the Users Group, nor to the Admin user. These
> two entities are common to every workgroup file in the world.
>
> There is a lot to setting up security. You can accomplish what you want,
> provided you implement security properly.
> The security FAQ is at
> http://support.microsoft.com/?id=207793
>
> Security Whitepaper
> http://support.microsoft.com/?id=148555
>
> Although the whitepaper is old, it contains information to help you
> understand security.
>
> I have also outlined the steps in detail at
> www.jmwild.com/AccessSecurity.htm
>
> >
> > What I want is to make sure that the user can only change the data on
> > a form and not on the table itself.
>
> You can deny users permission on the tables and have all data interaction
> occur via forms based on RWOP (run with owner permissions) queries - details
> in the FAQ.
>
> >
> > I won't mind if the user can open the tables, just don't want them to
> > change the data directly on the tables.
- Next message: Bob: "I will Pay for a Invoice/Statement template"
- Previous message: M.L. Sco Scofield: "Re: =Date()"
- In reply to: Joan Wild: "Re: Change data on Form and NOT on Table"
- Next in thread: Joan Wild: "Re: Change data on Form and NOT on Table"
- Reply: Joan Wild: "Re: Change data on Form and NOT on Table"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|