Permissions to view/not view particular data

[imelda1ab]

Can someone point me to a site or give me the proper search
terminology for figuring out how to apply security to particular
tables? Or maybe it can be set at a field level? Maybe what I want
to do is impossible - I'm out of ideas on how to search. Here's what
I'm trying to accomplish: I have created a Performance Evaluation
database containing professional, semi-professional and non-
professional employees. An Executive should be able to review the
professional/semi-professional but not the non-professional while an
office manager should have rights to review only the non-professional
evaluations.

As always I appreciate any and all comments and information.

 

[Jeff Boyce]

One approach to achieving this would be to create several different "views"
(in Access, queries) of the data, one for each "rights" group you're
considering.

Then, if you add a way to verify/validate the "rights" (a login process
comes to mind), you could use the appropriate query to display the
appropriate data...

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[imelda1ab]

One approach to achieving this would be to create several different "views"
(in Access, queries) of the data, one for each "rights" group you're
considering.

Then, if you add a way to verify/validate the "rights" (a login process
comes to mind), you could use the appropriate query to display the
appropriate data...

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.







- Show quoted text -

Maybe I eliminate the hassle and create two front-ends. Neither group
of managers is sophisticated enough to find the backend.

 

[Arvin Meyer]

Maybe I eliminate the hassle and create two front-ends. Neither group
of managers is sophisticated enough to find the backend.

That works, but makes it more difficult to maintain because you need to do
everything twice.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access
Co-author: "Access 2010 Solutions", published by Wiley