ChangeProperty Question

[irish634]

Hi all,

I am sure there is a much simpler way to do this, so any advice is appreciated.

In my security module, I set the following at startup:

    ChangeProperty "AllowToolBarChanges", DB_BOOLEAN, False
    ChangeProperty "AllowShortCutMenus", DB_BOOLEAN, False
    ChangeProperty "AllowSpecialKeys", DB_BOOLEAN, False
    ChangeProperty "AllowBuiltInToolBars", DB_BOOLEAN, False
    ChangeProperty "AllowFullMenus", DB_BOOLEAN, False
    ChangeProperty "AllowBreakIntoCode", DB_BOOLEAN, False

When I log in as an administrator, I change there properties to "true" however, I still can't change/access the menus/toolbars etc. I know that when I enable/disable the shift key, I need to restart the DB in order for the change to take effect. Is there a way to refresh the above properties without re-opening the database?

Or perhaps is there another idea that will give me the same result?

Thanks,
Craig

 

[KenHigg]

You could have an admin form/button or a macro that turns them on. Would that work?

 

[irish634]

You could have an admin form/button or a macro that turns them on. Would that work?

Well I am turning them on as the admin logs in. or are you talking about something else?

I presume I could hide/unhide the menubars/toolbars depending on which user level is logged in, but I also want to limit which user level can/cannot change toolbars etc.

 

[gemma-the-husky]

i dont know if there is a way round it

it sets the property for the NEXT login doesnt it - so you have to login twice to get what you want

 

[KenHigg]

Another way would be to turn them on as the db closes. Then the shift would bypass turning them off on open...

 

[irish634]

i dont know if there is a way round it

it sets the property for the NEXT login doesnt it - so you have to login twice to get what you want

That's what I thought too. Was just wondering if there was a way to refresh the current DB while it's open to skip all that.

Another way would be to turn them on as the db closes. Then the shift would bypass turning them off on open...

The shift key is also disabled at startup. I only allow the admins 1 time of opening with the shift key (unless they manually set it each time they close the DB).

I'll probably end up just toggling the menubars/toolbars depending on who is logged in. Not sure though. I'm still researching how others have done it.

 

[KenHigg]

I think the best way is to have an admin form that only admins can open. You can do this by have an invisible button that shows up if the user role is admin.

 

[irish634]

I think the best way is to have an admin form that only admins can open. You can do this by have an invisible button that shows up if the user role is admin.

I have a pretty good setup (I think anyway) that I can specify access to forms based on the user level. Seems to be pretty solid though I am not done with it. One of the open items is the subject of this thread, allowing admins the correct menus/toolbars.

I'll most likely end up toggling this stuff on/off, but we'll see. I am still debating how to do it. Basically, I can limit the access by disabling all the properties at start up. Then allowing the admin to enable the shift key then restarting the database to access the menus/toolbars.

I'm really trying to eliminate the need for an admin to restart the database for access to these properties, menu/toolbars.

 

[KenHigg]

Why not turn them off only if the user is NOT admin?

 

[irish634]

Why not turn them off only if the user is NOT admin?

Yes I can do that. I just need to disable the access to them.

 

[KenHigg]

I'm starting to get a headache -

 

[gemma-the-husky]

ken

the problem is that when you start up, the db window displays the settings according to the previous login --- so if you set it to say allow access to the database window. becuase you are an admin user, it still wont actually allow this until you close, and login again.

i had this with one client, and we dont bother --- the first time they login as users, they see some options which they cant run anyway - the second time, they disappear. it is only an issue when an upgrade is issued.

 

[KenHigg]

Ah.... I see.

I wouldn't even allow admins access that far in. Just have a devloper back door.

 

[irish634]

ken

the problem is that when you start up, the db window displays the settings according to the previous login --- so if you set it to say allow access to the database window. becuase you are an admin user, it still wont actually allow this until you close, and login again.

i had this with one client, and we don't bother --- the first time they login as users, they see some options which they cant run anyway - the second time, they disappear. it is only an issue when an upgrade is issued.

Sounds like it's not really worth it to do what I am thinking of. I'll just let the admins enable the bypass key and disable it on every start up. That will take care of what I want to do anyhow. Like I mentioned previously, I was just trying to circumvent the need to re-open the db.

Ah.... I see.

I wouldn't even allow admins access that far in. Just have a devloper back door.

I usually do that too, though I am basically handing this off after it's complete and I want it to be fairly simple for the admins to get into it if they need to.

 

[KenHigg]

I usually do that too, though I am basically handing this off after it's complete and I want it to be fairly simple for the admins to get into it if they need to.

If this is a contract gig maybe they'll screw up something and have to pay you to come back and fix it.

 

[irish634]

If this is a contract gig maybe they'll screw up something and have to pay you to come back and fix it.

Hmmm.... now there's an idea!
Got any ideas on how I can code that in?? Haha.

 

[KenHigg]

Hmmm.... now there's an idea!
Got any ideas on how I can code that in?? Haha.

If me.MyDate > 6/1/2009 then
msgbox "Critical error. Contact system administrator."
end if

 

[HiTechCoach]

Hi all,

I am sure there is a much simpler way to do this, so any advice is appreciated.

In my security module, I set the following at startup:

    ChangeProperty "AllowToolBarChanges", DB_BOOLEAN, False
    ChangeProperty "AllowShortCutMenus", DB_BOOLEAN, False
    ChangeProperty "AllowSpecialKeys", DB_BOOLEAN, False
    ChangeProperty "AllowBuiltInToolBars", DB_BOOLEAN, False
    ChangeProperty "AllowFullMenus", DB_BOOLEAN, False
    ChangeProperty "AllowBreakIntoCode", DB_BOOLEAN, False

When I log in as an administrator, I change there properties to "true" however, I still can't change/access the menus/toolbars etc. I know that when I enable/disable the shift key, I need to restart the DB in order for the change to take effect. Is there a way to refresh the above properties without re-opening the database?

Or perhaps is there another idea that will give me the same result?

Thanks,
Craig

Craig,

I am curious ... Sounds like your app is multi user. If it is, then Is you app split into a front end and back end?

 

[irish634]

Craig,

I am curious ... Sounds like your app is multi user. If it is, then Is you app split into a front end and back end?

Good point and I see where you are going with it. Yes it is. and yes it is.
Another hole to plug. LOL.

In theory, the users with the exception of the admins, should not be able to tell the app is split. So what I am doing is really over kill. As long as I can keep them from getting to the db window, I should be ok.

 

[HiTechCoach]

Good point and I see where you are going with it. Yes it is. and yes it is.
Another hole to plug. LOL.

In theory, the users with the exception of the admins, should not be able to tell the app is split. So what I am doing is really over kill. As long as I can keep them from getting to the db window, I should be ok.

Where I was going with my question is is that you could have different fronts ends for different users.

I also force all my users to open the front end (MDE/ACCDE only) in runtime mode.