What is RWOP and how can I create it?

  • Thread starter Thread starter Tintin via AccessMonster.com
  • Start date Start date
T

Tintin via AccessMonster.com

Hi,

I have same problem with Connie and Rick already answered nicely (below).
After days searching until get headached, I still don't get the idea how
what to do. Please someone explain to me step by step about what is "Run With
Owner's Permissions" queries" and how to create it.

Thanks,
Tintin
------------------------------------------------------------------------------
-------------------------------------------------------------------
Connie - 23 Aug 2005 17:28 GMT
Hello

We have a small database intended for retail sale. We have converted it to
an mde and have locked it down regarding security and startup options etc.
We have also hidden several of the critical tables and queries. The problem
is, if I open a new database in Access and have set my options correctly, I
can import all of the tables and queries.


Rick Brandt - 23 Aug 2005 17:57 GMT

You have to deny all permissions to tables and use "Run With Owner's
Permissions" queries instead. Then the tables cannot be imported and if a
user imports a query it is useless without the tables it is based on.
 
Tintin said:
Hi,

I have same problem with Connie and Rick already answered nicely
(below). After days searching until get headached, I still don't get
the idea how what to do. Please someone explain to me step by step
about what is "Run With Owner's Permissions" queries" and how to
create it.
Click to expand...

This only makes sense in the context of a file properly secured with Access User
Level Security. Do you have such a file and do you understand how user level
security works?

Once such a file exists you can allow or disallow users access to certain
objects. So (for example) you can deny access to a table for non-admin users.
Then you can create a query against that table while logged in as an admin user
that does have permission to use the table.

One of the properties of a query is "Run Permissions" and that can be set to
either "Owner's" or "User's". When set to User's then a user who logs into your
app and attempts to run the query will do so with his own permissions. Since he
does not have permission to the table the query is based on the query will not
work for him.

If the creator of the query sets that property to "Owner's" then the user will
be granted the same permissions as the owner of the query whenever he tries to
use it. Thus the query will allow access to data that is stored in a table that
the same user could not access directly.
 
Hi Rick,

Thanks for the prompt response.

I thougt this problem is not too complicated. I just want to email a small
mde file to my collague and I don't her to import the table of my database
from anotther new mdb application. In this case do I still have to go
through that ULS?

I don't have the ULS file and I don't know how ULS works. Is it difficult to
learn how to create such file? I hope you have a lot of patient to let me
know how to understand the ULS step by step (ugh... this problem make me
nervous and frustated).

Thanks,
Tintin


Rick said:
Hi,
Click to expand...
[quoted text clipped - 3 lines]
about what is "Run With Owner's Permissions" queries" and how to
create it.
Click to expand...

This only makes sense in the context of a file properly secured with Access User
Level Security. Do you have such a file and do you understand how user level
security works?

Once such a file exists you can allow or disallow users access to certain
objects. So (for example) you can deny access to a table for non-admin users.
Then you can create a query against that table while logged in as an admin user
that does have permission to use the table.

One of the properties of a query is "Run Permissions" and that can be set to
either "Owner's" or "User's". When set to User's then a user who logs into your
app and attempts to run the query will do so with his own permissions. Since he
does not have permission to the table the query is based on the query will not
work for him.

If the creator of the query sets that property to "Owner's" then the user will
be granted the same permissions as the owner of the query whenever he tries to
use it. Thus the query will allow access to data that is stored in a table that
the same user could not access directly.
Click to expand...
 
Hi Joan,

Thanks for being nice to me, I will study the link. I just reply to Rick's
suggestion and it seems that rwop is way beyond my knowledge.

Thanks,
Tintin

Joan said:
In addition to Rick's advice, read www.jmwild.com/rwop.htm You set this
property by opening a query in design view, then go to View menu and choose
Properties.[quoted text clipped - 23 lines]
tries to use it. Thus the query will allow access to data that is stored
in a table that the same user could not access directly.
Click to expand...
Click to expand...
 
RWOP is a non-starter if you haven't implemented security. You should
understand that security can be broken. Since you are sending your
colleague the file, there's really nothing you can do to stop them from
opening it or importing from it.

--
Joan Wild
Microsoft Access MVP
Tintin via AccessMonster.com said:
Hi Joan,

Thanks for being nice to me, I will study the link. I just reply to Rick's
suggestion and it seems that rwop is way beyond my knowledge.

Thanks,
Tintin

Joan said:
In addition to Rick's advice, read www.jmwild.com/rwop.htm You set this
property by opening a query in design view, then go to View menu and
choose
Properties.
Hi,
Click to expand...
[quoted text clipped - 23 lines]
tries to use it. Thus the query will allow access to data that is
stored
in a table that the same user could not access directly.
Click to expand...
Click to expand...
Click to expand...
 
Thanks again,

What a relieve to hear you explanation, at least I'm not stuck with uls or
rwop. Thanks for spending you time for me.

Regards,
Tintin

Joan said:
RWOP is a non-starter if you haven't implemented security. You should
understand that security can be broken. Since you are sending your
colleague the file, there's really nothing you can do to stop them from
opening it or importing from it.
Hi Joan,
Click to expand...
[quoted text clipped - 14 lines]
Click to expand...
 
Back
Top