Record Level Security

[Guest]

Background:

I have a database that contains records from multiple departments and
currently have a check that prevents departmental users from changing/edit
records that do not match their departmental code. Basically, it is stored
in an form where it checks if current users Dept code = records Dept code if
true than it is ‘ok’ to change the record…but if current users Dept code does
not = record Dept code ‘No’ change allowed. This has worked fine in the
past, but now certain departments are going to have the ability to modify
other department records and my little check is going prevent this from
happening. I was wondering if there is any type of security measures I can
use/add to place record level security to solve my new issue of allowing some
departments the ability to change other department records.

If your confused, imagine how I feel.

More background info:

The user must login using his/her USERID/PWD and there are limited security
groups in place on tables and forms.

Thanks in advance.

 

[Keith Wilby]

Background:

I have a database that contains records from multiple departments and
currently have a check that prevents departmental users from changing/edit
records that do not match their departmental code. Basically, it is
stored
in an form where it checks if current users Dept code = records Dept code
if
true than it is 'ok' to change the record.but if current users Dept code
does
not = record Dept code 'No' change allowed. This has worked fine in the
past, but now certain departments are going to have the ability to modify
other department records and my little check is going prevent this from
happening. I was wondering if there is any type of security measures I
can
use/add to place record level security to solve my new issue of allowing
some
departments the ability to change other department records.

If your confused, imagine how I feel.

More background info:

The user must login using his/her USERID/PWD and there are limited
security
groups in place on tables and forms.

Thanks in advance.

You need some way of matching the users with the records they should have
permissions to. Previously you've used department ID but now that's no
good. What other entity provides commonality between the users and their
records? Once you've identified this entity and stored it in each record
the rest should be easy.

Regards,
Keith.
www.keithwilby.com