Quake3World

lets say you have an application and you want to limit a form's functionality based on user permitions(no not the OS's permissions, but the permision set localy for that application).

it just seems like a mandane situation rearanging every form's control and function based on if's and then's according to the user.

is there a broadly accepted convention on how to handle situations like this, or is it flat out as simple as it looks: alot of exceptions set localy to te control or functionality?

I really hope I'm making my point clear on this one.

I'm thinking: save each user's permissions in a database, and eveytime a form/control loads and a function is called I have to check on the user database for the right permissions and make the changes on the spot for each situation.

I think what you need to do is look for some kind of broadly accepted convention to handle situations like that.

What if you setup a set of user types (like Admin, Manager, Supervisor, Employee) and then during the Form_Load you check to see which class the user is in and then just disable the controls based on that?

bitWISE wrote:What if you setup a set of user types (like Admin, Manager, Supervisor, Employee) and then during the Form_Load you check to see which class the user is in and then just disable the controls based on that?

I was thinking of handling it with groups but , there might be need for more detail.

I really don't see this as being a simple solution, it's just goign to take a butload of coding