User Level Settings Locked Me Out

thinair421

Registered User.
Local time
Today, 15:46
Joined
Jun 22, 2010
Messages
34
So, I have a rather huge problem right now. As of this morning my database was unsecured, so I decided to try and mess with/get used to the user level security settings/wizard...maybe not the best idea. What appears to have happened to me is that I can no longer edit my security settings because the only two users that I have only have user rights. Is this even possible? I would hope as a failsafe that access would require atleast one user with admin rights per database. Shift-starting didnt do anything...Any suggestions? Thanks in advance.
 
Can you open the db using another computer? Many rookies playing with workgroup security modify their computers system.mdw file instead of creating a new mdw file. You will be luckily if you made that simple mistake. If not, you will probably have to pay a company to hack into your database. Too late now but always remember to make backup copies of your database before making design changes.
 
First, I don't think you can delete the Admin account (because it owns the DB). But you could block it in various ways by removing its rights. If that is ALL you really did, there is some hope.

As long as you didn't change the database owner, you would be able to come in as the Admin account, which has the Admins (note: plural) group rights. There is no password on any accounts in a fresh copy of the workgroup file, so you might just squeak by. Here's how you do that.

Try going in to workgroup administrator utility to create a new blank workgroup file. Then use workgroup administrator to change to that file. Then try to open your database by just clicking on it.

If that doesn't do it, I agree with ghudson's comments.
 
Doc -

If they followed the proper design, the Admin user WOULD be removed from the Admins group. So it may not be available. If you don't remove the Admin from the Admins group when securing a database using Access User Level Security, then anyone with a system mdw file can log in as admin and nothing has changed.
 
OK so i opened it on another computer on the network, and logged on (to windows) using the same login i used to create the database in. Database no long has any security on it, and I have all admin rights. What is my next step here to safeguard my database from what almost just happened, and where did I go wrong...and how would I be able to access the file on the original computer? Thanks so much for the help guys, i owe you big time.
 
OK so i opened it on another computer on the network, and logged on (to windows) using the same login i used to create the database in. Database no long has any security on it, and I have all admin rights. What is my next step here to safeguard my database from what almost just happened, and where did I go wrong...and how would I be able to access the file on the original computer? Thanks so much for the help guys, i owe you big time.

copy the SYSTEM.MDW file from the other computer to yours, overwriting the existing one on your machine.
 
Alrighty, did that. No longer asks for a password on the "busted" computer, but still no <Tools> option in access...its still gone. Any suggestions now?

EDIT: On my computer it is saying that I don't have exclusive access to the database, and when I try to save its telling me someone else has the DB open, but I know that no one does. On the brighter side, I got <Tools> back in my menu. But please help if possible. Im on the clock here and cant edit my database (and save it) until this is resolved. Thanks so much
 
Last edited:
If you know absolutely that nobody else has the DB open, you have a "floating" .LDB file that you need to delete (while you are not in the DB yourself). It will have the same name as the .MDB and will be in the same folder. Trash it.
 

Users who are viewing this thread

Back
Top Bottom