Re: Securing Tables From Data Changes
- From: "Rick B" <Anonymous>
- Date: Fri, 13 May 2005 11:40:39 -0500
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.
The Microsoft Security white pages has more details on this, if I remember
correctly.
--
Rick B
"jkmccnh" <jkmccnh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3843FC8A-56E4-4A11-9B73-F33A7CB9B599@xxxxxxxxxxxxxxxx
> I have an app that must log all changes to data (who, when, what). The
> problem is securing the tables so someone with Access know-how can't use
the
> shift key (bypass start-up options) to get to the tables and change data
> without a log entry being created. Access 2000 front end linked to SQL 7
back
> end. MDE will only secure the forms and reports. Thought of making the
tables
> hidden but again, someone with access knowledge will know how to turn them
> back on. Is there a way to generate a log entry when the table is directly
> accessed? Any other suggestions??
.
- Follow-Ups:
- Re: Securing Tables From Data Changes
- From: Joan Wild
- Re: Securing Tables From Data Changes
- References:
- Securing Tables From Data Changes
- From: jkmccnh
- Securing Tables From Data Changes
- Prev by Date: Securing Tables From Data Changes
- Next by Date: Re: Securing Tables From Data Changes
- Previous by thread: Securing Tables From Data Changes
- Next by thread: Re: Securing Tables From Data Changes
- Index(es):
Relevant Pages
|
Loading