Question Control panel to change custom permissions Access 2007

[vapid2323]

Hey guys,

I need some ideas on how to create a control panel that my company’s leadership can access to make custom permissions, or change the default permissions.

Currently I am working with Access 2007 and I have created the basics of the DB already. It is a full Management DB that my boss asked me to create. It manages my status forms, Quality Monitors (This is a call center), new hire information requests etc it covers quite a bit of information and with all that info I need to limit access.

I have created a basic authentication system that asks for a password and uses the network login name for a username. After login it opens a hidden form that I can pull from to query the tables.

So with my looking around I came across a solution that is not directed for my exact problem but I am thinking about adapting it.

http://allenbrowne.com/ser-55.html

This is used to lock out fields from being used, but I thought I might be able to change it to fit my needs and add in options to prevent things from being visible.

Do you think I can use this as a viable solution?

How might you solve this issue?

Thank you for any help!

 

[Galaxiom]

Allen's solutions are usually very powerful. Sometime they go a lot further than required. Whether it is what you want demends on how far you want to go. Sometimes too much control makes the maintenence of security a chore.

I haven't looked at the sample but it sounds like if you change the code from working with the Locked property to working with the Visible property it would do what you want.

I have done really simple security by assigning a secury level to users. This is set up in a form. Each contol on the other forms has the minimum security level required to view that control stored in its Tag property. All controls are set to Not Visible in the design view.

The OnLoad event loops through the controls and makes them visible if the user's security level is equal or higher than the level stored in the control's tag.

It does mean the setting of the security level of the control is a design task so it is not ideal. Crude but effective.

However no matter what you do you need to stop the users getting directly to the tables. The only real security for this is by using an SQL backend. Anyone who knows what they are doing can get around other simple techniques.

 

[vapid2323]

Thank you for that!

I do think I can change the code to fit my needs just need to play around with it.

I am not sure who will have access to the control just yet but I really hope that this dosent turn into a management nightmare.

Anyone one have any other tips before I spend a few hours on this lol