J
JohnC
I have an application with User Level Security. There are two tables with a
one-to-one relationship. This was designed so that different permissions
could be assigned to users depending on whether they could edit one or the
other table.
I am finding that this degree of security is probably not needed and I would
like to combine the two tables into one. This is in part being driven by a
need to simplify and reduce database objects.
The application will still have User Level Security. I want to still
restrict what users can edit or not edit and I think I want to do this using
the form. So I want the form to recognize the user, determine what group
they belong to, and enable/disable controls accordingly.
Can somebody point me in the right direction? Is this described in a book?
Thanks for your help.
John C
one-to-one relationship. This was designed so that different permissions
could be assigned to users depending on whether they could edit one or the
other table.
I am finding that this degree of security is probably not needed and I would
like to combine the two tables into one. This is in part being driven by a
need to simplify and reduce database objects.
The application will still have User Level Security. I want to still
restrict what users can edit or not edit and I think I want to do this using
the form. So I want the form to recognize the user, determine what group
they belong to, and enable/disable controls accordingly.
Can somebody point me in the right direction? Is this described in a book?
Thanks for your help.
John C