Database refuses all users

[Eyespi20]

Don't know what or how, but the database won't allow anyone to open it -- says nobody has permissions. When we right click it and view security, there are all kinds of people who are allowed full control. We can log into the system as administrator and are still refused.

Can anyone shed any light on how to get around this?

Thanks in advance.

Margaret

 

[jhall01]

Have you tried importing data into a new DB?

 

[Eyespi20]

Yes, same refusal of access.

Margaret

 

[MoLaker]

The permissions being referred to in the message sound like Access security permissions. The permissions you are viewing when you right-click and view security are Windows NTFS permissions. Not the same.

Before the problem cropped up, were you prompted for a UserID and password when you opened the database? If so, are you now?

 

[Eyespi20]

Problem solved -- db was moved from the folder it was created in. When it was moved back, it allowed us in.

MoLaker -- yes, it did prompt for UserID and Pword and no, it just popped up the denial of access message.

Thanks all for the help.

Margaret

 

[MoLaker]

If you look at the folder where the DB resides, you may find a file with the extension .MDW. Likely, it has the same name as the DB. If this is the case, it is probably the workgroup file for that DB and you are assigned to it automatically through a command-line switch. It sounds like by moving the DB, you were not being joined to the proper workgroup. Take a look at the shortcut you normally use to access the DB. Do you see something like ""C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "C:\[pathToDB]\[DBName].mdb" /wrkgrp [path to workgroup file]\[workgroup file].MDW"? When the DB was moved, did you just create a new shortcut to the DB?

 

[Eyespi20]

No, she just did a drag-n-drop to it.

Yes, there is the .mdw file and it was moved with the db.

Margaret

 

[MoLaker]

No, she just did a drag-n-drop to it.

So, the shortcut you used did not have the command-line which assigned the workgroup. Regardless of whether or not the workgroup was in the same directory as the DB, you were not being assingned to it. Consequently, you were using the default workgroup (system.mdw) which resides on your computer - and logs on as ADMIN automatically. Usually ADMIN has all permissions removed from a database when it is secured. Consequently, logging on as ADMIN would result in "No Permissions".