Another alternative:
ensure each control and form has a property that can be used to store a
security ID
set up a table of secured items that consists of the security ID and a
description.
set up a table of users.
set up a table of security access which has the security id and the user
id and their level of access (I normally use None, Read Only or Full).
then code in an appropriate place (form's load, object's refresh, maybe)
to check for the currently logged in user's access level for any object
with a security ID.
You could also add in groups and exceptions to this.
Frank.
Frank Cazabon
On 14/05/2018 01:29 AM, Ajoy Khaund wrote:
Hi All,
In my applications I have added a user table where there will be field to
define the user level.
Level - 1 Admin: can add users and has access to all
Level - 2 Manager - cannot add user but has access to all others
Level - 3 Operator - can add transactions but cannot create masters (eg.
add/edit a customer)
Now in the master entry forms in the Add & Edit button I can put some code
to prevent
Level 3 users from adding or editing.
I want Level - 3 users to be able to view the masters. So for them add &
edit button will be disabled
or some code will b there to tell them they have no access.
Is there a better way?
Any ideas which u are implementing are welcome.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/f304cf76-270a-4a06-b893-054556508...@gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
