Glitch in user-level security for one user

PaulA

Registered User.
Local time
Today, 23:02
Joined
Jul 17, 2001
Messages
416
Hi, all -

We have an mdb database used through Access 2007 and we have a user-level security process with it. One of my users (and only one, and she is my primary onsite administrator) is having a strange recurring situation where her account will disappear so she can't log in. Then, without doing anything, her account will seem to reappear so she can log on again - but but her Admin permission group has been removed, only the User group is there which has had all permissions removed. She gets the error about not having permission to open the Autoexec function. I have to go in and reassign her to to the Admin group.

Not sure why this is happening. She is the only one that this is happening to.

Has anyone out there experienced something like this?

Thanks.
 
When the database is secured, the Admin user is removed from the Admins Group. Access rights to all objects will be removed for Users Group as well.

This is important because all users are members of the Users group by default and Users Group have full access to all objects of the database.

After these two steps individual User Account or users belong to a particular Group Account are assigned permissions on Objects (Tables, Forms, Reports etc.) depending on their mode of activity.

Separate Admins Group Account(s) (e.g. MGRGRP - manager group) can be created with full access rights to all objects and User Accounts can be joined to this group.

Check whether your database is secured by following these methods or not.

For more details visit this link: Microsoft Access Security

Perhaps you will be able to figure it out yourself, what exactly your database issue is.

If the database and Workgroup Information files are located on a common Network Server, check the access status of your Admin user with the Network Administrator, whether she has any access privilege issue with the Server that makes up the On and Off Login issue.
 
Last edited:
is the mdw file itself getting corrupted/replaced/re-copied somehow?

that might explain it.


I assume you aren't using system.mdw, and that you have secured against a purpose-built mdw file.
 

Users who are viewing this thread

Back
Top Bottom