Re: Securing Tables From Data Changes
- From: "Joan Wild" <jwild@xxxxxxxxxxxxxxxx>
- Date: Fri, 13 May 2005 12:57:52 -0400
"Rick B" <Anonymous> wrote in message
news:uqhYAq9VFHA.1044@xxxxxxxxxxxxxxxxxxxxxxx
> One way is to implement user-level security and take away the user's
> access
> to the tables. This will mean they can't open or modify the tables in any
> way. Also, take away all access to the queries. Then, give them the
> needed
> access to the various forms they should be using.
>
> Since the forms are based on queries that they don't have access to, you
> would get an error UNLESS, you set the queries to "run with owner
> permission". Then, when they open the form, they will be able to use the
> queries and perform the needed tasks.
Not quite. They'll still need at least read data permission on the RWOP
query in order to be able to read data. And it they need to
add/modify/delete records in the form, then they'll need the appropriate
permission(s) on the query.
--
Joan Wild
Microsoft Access MVP
.
- Follow-Ups:
- Re: Securing Tables From Data Changes
- From: jkmccnh
- Re: Securing Tables From Data Changes
- References:
- Securing Tables From Data Changes
- From: jkmccnh
- Re: Securing Tables From Data Changes
- From: Rick B
- Securing Tables From Data Changes
- Prev by Date: Re: Securing Tables From Data Changes
- Next by Date: Re: MSysTables
- Previous by thread: Re: Securing Tables From Data Changes
- Next by thread: Re: Securing Tables From Data Changes
- Index(es):
Relevant Pages
|