User Table/Query Access question

[jayson.cervantes]

To set the stage: I have an access database with security controled by
a .mdw file. I have user "John" who has Read/Update/Insert access to a
table but currently can do those functions through a form as he has no
access to the table itself because the database window is disabled. The
form that he uses to update the table locks certian fields from him so
he cannot update certian elements.

My issue is that I need to give John the ability to write queries from
the data in the tables but I do not want him to be able to update data
in these tables directly (something he could do through a query or by
directly updating the table) once he gets access to the Database
window.

How can I keep him as a user of the application where he can only
update the table through my form but he is free to create queries and
run queries on the tables?

Thanks,
Jason

 

[Pieter Wijnen]

AFAIK Oracle is the only player that gives you the possibility to assign
Column level security
an Access workaround is to add WITH OWNERACCESS OPTION to the end of the
Form's Recordsource (Query)
and revoke anything but "read" access to the underlying Table for the
User/Group

HTH

Pieter

 

[Pieter Wijnen]

AFAIK Oracle is the only player that gives you the possibility to assign
Column level security
an Access workaround is to add WITH OWNERACCESS OPTION to the end of the
Form's Recordsource (Query)
and revoke anything but "read" access to the underlying Table for the
User/Group

HTH

Pieter

To set the stage: I have an access database with security controled by
a .mdw file. I have user "John" who has Read/Update/Insert access to a
table but currently can do those functions through a form as he has no
access to the table itself because the database window is disabled. The
form that he uses to update the table locks certian fields from him so
he cannot update certian elements.

My issue is that I need to give John the ability to write queries from
the data in the tables but I do not want him to be able to update data
in these tables directly (something he could do through a query or by
directly updating the table) once he gets access to the Database
window.

How can I keep him as a user of the application where he can only
update the table through my form but he is free to create queries and
run queries on the tables?

Thanks,
Jason

--

 

[jayson.cervantes]

Im faking colum level security by having the form look at the user's
groups and determining what fields to unlock/lock. Thats not the issue.
I want to give this guy the ability to create read-only queries and not
allow him to update tables/queries directly.

Thanks,
Jason

 

[Pieter Wijnen]

If your queries include WITH OWNERACCESS OPTION you can revoke DML rights
from the underlying table & give him the rights he needs per query instead.
He will then not be able to make updatable queries.

Another way would be to give him a seperate Db with all the tables linked &
provide him with read only access to the tables in that

Pieter

Im faking colum level security by having the form look at the user's
groups and determining what fields to unlock/lock. Thats not the issue.
I want to give this guy the ability to create read-only queries and not
allow him to update tables/queries directly.

Thanks,
Jason

--