Permissions changing on their own

[mbentley]

I have a split database with frontend user-level security and two user groups: Full and Admin (and of course the default Users group). I've removed all permissions from the Users group and given the appropriate permissions to the Full and Admin groups. I'm having something strange happen with my permissions when I make updates to the end users' frontends.

Since I'm using MDE frontends, I have to log in as the administrator, create a new database and import all the objects when I want to make updates (see other posts on this topic if you're wondering why I have to do it this way...it's a long story). This works as it should, except that the Full group loses all permissions and the User group gets the same permissions as the Admin group (all permissions). The Admin group is unaffected. It's almost as if it's resetting the permissions to the defaults.

It's not a big deal, as all I have to do is fix the permissions and they stay the same until the next update. I'm just wondering if anyone else has experienced this and whether there was a way around it.

 

[RichMorrison]

You wrote
<<
It's almost as if it's resetting the permissions to the defaults.
>>

Yes that's what happens when you create a new MDB.

So, *before* you import anything, set the permissions for "New" objects under each category. Then import.

Or
(the better way) keep a backup copy of the front end "source" MDB. Modify it and convert to MDE. Install for users.

RichM

 

[mbentley]

Thanks Rich. That makes sense. I do keep an unsecured MDB on my system, but I have to MDE it after I install because I need to make a code change specific for each system when I install. (I won't get into a long story about why that is...I just couldn't make the code 100% generic. Just 99.9999%.)