Re: rwop

Here's another tip for you. You can create a RWOP query for each of your
tables, and remove all permissions from the tables for users. Use these
base queries as the basis for all other queries/forms/reports. Only the
base queries need to be RWOP; the queries based on these do not.

--
Joan Wild
Microsoft Access MVP

hireagenius via AccessMonster.com wrote:
Joan,Thanks once again for your response. That does help.

Your clarification of rwop does help me think through the process,
esecially concerning how I have set the permissions for users. If my
query doesn't work, it may not be the query itself, it could be how I
have set up the security.

I had a question for you but as I articulated it, the answers began
coming to me so I am ready to test my logic. You don't know how much
you have helped. Having someone to ask these questions to forces me
to clarify in my own mind what I need to do. Beforehand, I was
thinking that the rwop would prevent users from entering data, but
no, they will have owner's permissions. That was what I meant
regarding the cart and horse. How can users view data they entered if
they can't enter data. Your explanation of rwop really helped. I
guess I was thinking that it meant with permission of the owner not
with the permissions of the owner. With that and the CurrentUser()
i am ready to begin.

Thank you
Charlie


Joan Wild wrote:
RWOP

Run With Owner Permissions

This means run the query as though the query owner was running it.

It allows you to remove all permissions for users on the tables.

Now if you create a query against those tables, the user won't be
able to run that query, because they don't have any permissions on
the underlying tables.

By putting WITH OWNERACCESS (making it RWOP) on the query, you are
saying 'allow the user to run this query as though I, the owner of
the query, am running it'.

The owner of a query most often has full permission on the tables,
so this allows the user to run the query.

RWOP doesn't automatically mean that the user has all the
permissions that the query owner does. You still need to assign
appropriate permissions on the *query* in order for the user to run
it. So you could assign read data permissions on the query, and
they'll only be able to read data, even though the owner has full
permissions on the underlying table(s).

Furthermore, if the query owner has only read data permissions on the
underlying tables, they can't assign update/insert/delete
permissions on the query and expect that to succeed. The user
running the query will still be restricted by the owner's
permissions on the underlying queries.

Does that help?

Hi again Heros,
I have reviewed the threads on RWOP queries, and that section in
[quoted text clipped - 19 lines]
--
Message posted via http://www.accessmonster.com

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200603/1


.

Relevant Pages

  • Re: RWOP query with parameters
    ... such a query is only designed to be run with the referenced form ... an RWOP via code then you stand the danger of altering the "owner". ... You could have a basic RWOP stored of course, ... If you write a SQL statement in the Recordsource and save ...
    (microsoft.public.access.security)
  • Re: rwop
    ... Your clarification of rwop does help me think through the process, ... If my query doesn't ... users from entering data, but no, they will have owner's permissions. ... permissions of the owner. ...
    (microsoft.public.access.security)
  • Re: Security without signon
    ... I have never had to give the query owner explicit permissions on the tables. ... Your super user should not need to inherit any permissions from any group, ...
    (microsoft.public.access.security)
  • Re: Security without signon
    ... > When you are using a workgroup file in which the owner of the RWOP ... > query /does/ exist, the query would also have the permissions of all ... For example, the RWOP ... The query would only have permissions for the BlahBlah group, ...
    (microsoft.public.access.security)
  • Re: Secured Temp database
    ... > 1) I thought that the word "Owner" in RWOP meant the owner of the backend ... > tables not the front-end query. ... workgroup files, remember that a user /can/ be a member of several ...
    (microsoft.public.access.security)