[AccessD] Automating parameterized action queries.....

Heenan, Lambert Lambert.Heenan at AIG.com
Fri Mar 11 10:39:51 CST 2005


If you want to use Access security to deny access to the tables (for
writing) then you would also have to have all the other queries used by
forms etc. be set up as RWOP (Run With Owners Permissions) so that the
queries used for updating data will be able to do so. But then you are back
to square one. How to prevent the users using the RWOP queries to gain
access to the tables to change the data?

Lambert

> -----Original Message-----
> From:	accessd-bounces at databaseadvisors.com
> [SMTP:accessd-bounces at databaseadvisors.com] On Behalf Of John W. Colby
> Sent:	Friday, March 11, 2005 6:51 AM
> To:	'Access Developers discussion and problem solving'
> Subject:	RE: [AccessD] Automating parameterized action queries.....
> 
> BTW, you can create base queries, one for each table, which simply do a
> SELECT * FROM TBLX.  Then open the properties for the query and make it a
> snapshot query.  Now have them use those base queries instead of using the
> table directly.  Because the base queries are snapshot queries, no data
> can
> be changed.  
> 
> If they go around those queries to use the tables all bets are off.  You
> could of course use Access security to give them access to the queries but
> not the tables.
> 
> John W. Colby
> www.ColbyConsulting.com <www.ColbyConsulting.com>  
> 
> Contribute your unused CPU cycles to a good cause:
> http://folding.stanford.edu/ <http://folding.stanford.edu/> 
> 



More information about the AccessD mailing list