Solved VBA code to Disable multiple selection of commands

[alvingenius]

you are doing it manually, I thought it was based on the user's access?

i'm trying it first then i'll apply it based on user

I think the o/p is trying to get it working in a simple way, before trying to apply it to the real system.?

thats right
thanks

 

[The_Doc_Man]

First rule: If it works for you and you understand it, there is immediate merit to it. That right there is a good thing.

Second rule: Even if it is terribly sloppy then as long as it continues to work, you can put it on your "fix when I can get to it" list. The main operative rule is "If it ain't broke, don't fix it." But that rule says nothing about "if it ain't pretty."

 

[isladogs]

I can't open Colin's DB as I only have 2007, but the links states

Hi Gasman
I've just uploaded a MDB version of the utility which you should be able to convert back to an ACCDB that will work for you
See https://www.access-programmers.co.uk/forums/showpost.php?p=1634737&postcount=10

 

[Gasman]

Hi Colin,

Thank you for that, however I was able to open the later db you posted in post #17?
Plus I know the basics of how it works, from previous posts in other threads.

Thank you for going to that trouble though.

Edit:I've downloaded it anyway, as your code would be better than mine and it is a black box routine anyway.

 

[Mark_]

i'm trying it first then i'll apply it based on user

If you have not started work on your security table, I'd suggest getting some input if this will be a "User" based system, a "role" based, or a hybrid.

User based means you decide for a USER which forms/what controls on which forms you allow.

Role based means you decide for a ROLE which forms/what controls on which forms you allow, then assign a ROLE or ROLES to a user.

For both, I'd recommend having the default be "Seen nothing, Do Nothing" until they are allowed. This avoid a lot of headaches when users get access to things they shouldn't, but means you need to really make sure people are granted access to forms/controls as they are added.

 

[alvingenius]

If you have not started work on your security table, I'd suggest getting some input if this will be a "User" based system, a "role" based, or a hybrid.

User based means you decide for a USER which forms/what controls on which forms you allow.

Role based means you decide for a ROLE which forms/what controls on which forms you allow, then assign a ROLE or ROLES to a user.

For both, I'd recommend having the default be "Seen nothing, Do Nothing" until they are allowed. This avoid a lot of headaches when users get access to things they shouldn't, but means you need to really make sure people are granted access to forms/controls as they are added.

That's what i'm doing

i'm disabling all controls and enable em by users
Thanks

 

[The_Doc_Man]

For a small number of users, that is not a big issue. However, if your user base grows and you enable by user, you have to go back for each new user and do something potentially complex. It is your system, you know how it will be used, but ...

If you decide to go by ROLE then you program all the roles one time. Then when you add a new user, you add their names to your "approved users" list AND include a field that identifies the role they play. One change and done.