Run with Owner's Permissions

  • Thread starter Thread starter croy
  • Start date Start date
C

croy

I have my Access 2002 query defaults set to RWOP.

If I start a new form and base it on a linked table, the
resulting SQL contains the "Run with..." statment, but it
doesn't seem to be effective. Lesser users aren't getting
the benefits of "Run with...". Is it actually necessary to
have a saved query, even tho the SQL has the "Run with..."
statement?
 
Yes, you need to use a saved query. RWOP is a non-starter if you are using a SQL statement as the recordsource or modifying the SQL in code.

The statement in these cases is 'owned' by the user running it, as that is when a temp query is created. Since the user running it doesn't have permissions on the tables, it doesn't work.

If you create a RWOP query for each of your tables, you can then use SQL statements with these RWOP queries, and then you don't need a saved query for every recordsource.

--
Joan Wild
Microsoft Access MVP
:I have my Access 2002 query defaults set to RWOP.
:
: If I start a new form and base it on a linked table, the
: resulting SQL contains the "Run with..." statment, but it
: doesn't seem to be effective. Lesser users aren't getting
: the benefits of "Run with...". Is it actually necessary to
: have a saved query, even tho the SQL has the "Run with..."
: statement?
:
: --
: croy
 
Yes, you need to use a saved query. RWOP is a non-starter if you are using a SQL statement as the recordsource or modifying the SQL in code.

The statement in these cases is 'owned' by the user running it, as that is when a temp query is created. Since the user running it doesn't have permissions on the tables, it doesn't work.

If you create a RWOP query for each of your tables, you can then use SQL statements with these RWOP queries, and then you don't need a saved query for every recordsource.
Click to expand...


Thanks for the confirmation, Joan.
 
Back
Top