Securing ONE database

3 May 2006 3:21 PM

natalie

All I want to do is allow users to enter the database at switchboard, click
in to a data entry form/subform and add, edit, or delete INPUTTED DATA ONLY!
I do not want users to have access to update, insert, or delete data at table
datasheet view. But when I disallow those functions, inputted data on form
cannot be changed either. Can anyone provide moron-proof step-by-step
instructions before my entire head turns grey? Much obliged.

3 May 2006 3:31 PM

Rick B

Typically, you'd take away all access to the table. Then create a query
that pulls the data you want to use. Take away all access to that query.
Set the query property to "run with owner's permission". Build your form
and base it on that query.

For more information, do a search and read the previous posts on "RWOP".

Of course, to do all of this you will have to have your database properly
secured. If you try to open the database on another computer, make sure
that you get an error stating that the needed workgroup file is missing. A
lot of people secure a file on their computer, but then find that any one on
another computer can open it. This happens when you don't follow all the
steps in the security white pages.

--
Rick B

Show quoteHide quote

"natalie" <nata***@discussions.microsoft.com> wrote in message
news:FFA56EDE-D80B-4080-B353-F8E7E55589A9@microsoft.com...
> All I want to do is allow users to enter the database at switchboard,
> click
> in to a data entry form/subform and add, edit, or delete INPUTTED DATA
> ONLY!
> I do not want users to have access to update, insert, or delete data at
> table
> datasheet view. But when I disallow those functions, inputted data on
> form
> cannot be changed either. Can anyone provide moron-proof step-by-step
> instructions before my entire head turns grey? Much obliged.

3 May 2006 3:50 PM

Joan Wild

Rick,

Rick B wrote:

> Typically, you'd take away all access to the table. Then create a
> query that pulls the data you want to use. Take away all access to
> that query. Set the query property to "run with owner's permission". Build
> your form and base it on that query.

That is not correct. You can't take away all access to the RWOP query! The
users need at least read data permissions (and update, insert, delete
permissions if needed) on the query. The RWOP means that although the user
doesn't have permissions on the underlying table(s), let them run this query
as though the owner is running it (i.e. the owner does have the permissions
on the tables). The users still need permissions on the query object,
though.

--
Joan Wild
Microsoft Access MVP

3 May 2006 3:58 PM

Rick B

Oops. Sorry about that. Joan is the Security wiz, so I'm glad she was
watching!!

--
Rick B

Show quoteHide quote

"Joan Wild" <jwild@nospamtyenet.com> wrote in message
news:u4jVflsbGHA.1320@TK2MSFTNGP04.phx.gbl...
> Rick,
>
> Rick B wrote:
>> Typically, you'd take away all access to the table. Then create a
>> query that pulls the data you want to use. Take away all access to
>> that query. Set the query property to "run with owner's permission".
>> Build your form and base it on that query.
>
> That is not correct. You can't take away all access to the RWOP query!
> The users need at least read data permissions (and update, insert, delete
> permissions if needed) on the query. The RWOP means that although the
> user doesn't have permissions on the underlying table(s), let them run
> this query as though the owner is running it (i.e. the owner does have the
> permissions on the tables). The users still need permissions on the query
> object, though.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>

3 May 2006 4:59 PM

natalie

If I take away access to the table and replace the data entry part with a
query, then how will my table get updated? The data entry form consists of 3
subforms and all of my other queries and reports are based on a table. And I
am having the problem you discussed next: the file is secured when I open it
on my computer but not when another worker opens it on theirs. I'm not sure
why, though, because the file is on a network. What did you mean by
following the steps in the security white pages? What are these white pages
and steps and where can I find them?
Thanks for all your help! It is becoming somewhat more clear.

Show quoteHide quote

"Rick B" wrote:

> Typically, you'd take away all access to the table. Then create a query
> that pulls the data you want to use. Take away all access to that query.
> Set the query property to "run with owner's permission". Build your form
> and base it on that query.
>
> For more information, do a search and read the previous posts on "RWOP".
>
> Of course, to do all of this you will have to have your database properly
> secured. If you try to open the database on another computer, make sure
> that you get an error stating that the needed workgroup file is missing. A
> lot of people secure a file on their computer, but then find that any one on
> another computer can open it. This happens when you don't follow all the
> steps in the security white pages.
>
>
> --
> Rick B
>
>
>
> "natalie" <nata***@discussions.microsoft.com> wrote in message
> news:FFA56EDE-D80B-4080-B353-F8E7E55589A9@microsoft.com...
> > All I want to do is allow users to enter the database at switchboard,
> > click
> > in to a data entry form/subform and add, edit, or delete INPUTTED DATA
> > ONLY!
> > I do not want users to have access to update, insert, or delete data at
> > table
> > datasheet view. But when I disallow those functions, inputted data on
> > form
> > cannot be changed either. Can anyone provide moron-proof step-by-step
> > instructions before my entire head turns grey? Much obliged.
>
>
>

3 May 2006 5:47 PM

Joan Wild

natalie wrote:

> If I take away access to the table and replace the data entry part
> with a query, then how will my table get updated?

That'll happen automatically. Your query is based on the table, edits you
make in the query will be stored in the table.

The data entry

> form consists of 3 subforms and all of my other queries and reports
> are based on a table. And I am having the problem you discussed
> next: the file is secured when I open it on my computer but not when
> another worker opens it on theirs. I'm not sure why, though, because
> the file is on a network. What did you mean by following the steps
> in the security white pages? What are these white pages and steps and
> where can I find them?
> Thanks for all your help! It is becoming somewhat more clear.

It's a good sign that others can't open the mdb file without using the
correct workgroup.
Resources:
Security FAQ
http://support.microsoft.com/?id=207793

Security Whitepaper
http://support.microsoft.com/?id=148555

Although the whitepaper is old, it contains information to help you
understand security.

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm

--
Joan Wild
Microsoft Access MVP