Help! Locked out of all databases after testing security...

[Amit]

MS Access 2K, Windows XP
======================
Hi,

So, I am in deep trouble. I was trying to create a workgroup file on my
desktop to test it, and somehow, I've managed to lock myself out of all
databases. When I try to open any database now, it shows a logon screen with
my Windows login username displayed, and asks for a password.

What I did
========
I followed the steps from Joan's website (but obviously, I messed up somehow).

1. I ran wrkgadmn.exe from Start-->Run
2. Created a new file, entered a Name, Company and Workgroup ID.
3. Saved the file using a different name "TESTSYSTEM.MDW" on the C: drive in
a different folder.
4. Opened Access and went to Tools-->Security-->User and Group Accounts.
5. Created a new user with the name "amit" and a PID "1234".
6. Added the Admin group to this user by selecting "amit" from the user
drop-down list and then clicking on Add button.
7. Selected the "Admin" user from the drop-down list and removed Admin from
the Admin group.
8. Went to Change Logon Password and entered a password "test" for Admin.
9. Closed Access.
10. Tried to open Access and I got the Logon window with my name in the
Login/Username and empty password box.

I think I may have messed up somewhere in step 7. and/or 8.

The strange thing is that the user name displayed is my Windows login name,
and not the new username I created ("amit").

I tried opening other database files by double-clicking on them, and get the
same Logon window.

I've checked the ng and there are a few "locked out of db" posts, but from
what I can tell, nothing that fits my situation.

When I do a search for *.MDW on C: I get the following results:
1. TESTSYSTEM.MDW where I saved it (the file I created).
2. system.mdw (C:\WINDOWS\system32\)
3. SYSTEM.MDW (C:\Program Files\Common Files\System\)

When I run wrkgadmn.exe, I get the information for the file with the same
"Name" and "Company" as the original MDW file, before I created the new file
with different "Company" (I used the same "Name" though - name of
organization where I work), but the path name (not all of it is visible)
points to the location of the new workgroup file I created.

OK. In the spirit of adventure, I ran wrkgadmn.exe and clicked on "join" and
navigated to the SYSTEM.MDW file (3. in the above list) and clicked OK.

But, I'm still getting the same logon screen when I try to open a database.
I can open Access, but if I try to go to Tools-->Security-->User and Group
Accounts, I get the same logon screen.

If anyone can help me with this, I'll appreciate it a lot. Also, if you can
point out the error I made, maybe I can learn something....

Many thanks.

-Amit

 

[Amit]

Hi,

Panic alarm off!

I think I was totally thrown off on seeing my Windows login name in the
logon window and somehow assumed the worst. I *am* able to log into _all_
databases (not just the one I was testing) by using either "Admin" with the
password, or "amit" with no password.

I still haven't completed all the steps to secure the db, and even after
changing the workgroup file to the original one (SYSTEM.MDW), I still get the
logon screen for all the databases that I try to open.

Shouldn't the databases now open using the default mdw file, and not give
the logon screen?

Reading the 'Final Steps', I see that it says "this will ensure that you are
joined to the standard system.mdw for all sessions of Access.".

Does that mean till I complete all the steps, if I try to open any other
database, I'll get the logon window? I guess there is no way to get around
this...

If I delete the new workgroup file I created, will that make things go back
to not getting the logon screen on opening other databases?

Thanks!

-Amit

 

[Joan Wild]

Hi,
I still haven't completed all the steps to secure the db, and even after
changing the workgroup file to the original one (SYSTEM.MDW), I still get
the
logon screen for all the databases that I try to open.

Shouldn't the databases now open using the default mdw file, and not give
the logon screen?

You used wrkgadm.exe to rejoin the system.mdw. You didn't say which one
(windows system folder, or the program files...folder), but try joining the
other one.

Yes once you join the pristine system.mdw workgroup, you'll no longer get a
login prompt.

If you still are getting a login prompt, then a password has been set for
the Admin user in that workgroup.

 

[Amit]

You used wrkgadm.exe to rejoin the system.mdw. You didn't say which one
(windows system folder, or the program files...folder), but try joining the
other one.

SYSTEM.MDW (C:\Program Files\Common Files\System\) is the one I joined. And,
I am stil getting the Logon/password prompt for ALL databases.

I'll try joining the other one and see what happens.

Yes once you join the pristine system.mdw workgroup, you'll no longer get a
login prompt.

If you still are getting a login prompt, then a password has been set for
the Admin user in that workgroup.

How can I unset the password? Will deleting both the "system.mdw" files and
re-starting my computer somehow regenerate the original "system.mdw" file? I
remember reading that in the ng somewhere.

Will deleting the new file ("TESTSYSTEM.MDW") undo this?

Mind you, I still haven't completed all the steps mentioned on your web-site
(I also mentioned this in my post above). So, I'm still opening the database
(the original one I set out to secure, and all others) by clicking on the
file. Your website mentions that in the final steps, creating a short-cut
will ensure that I am joined to the standard system.mdw for all sessions of
Access (for other unsecured databases).

Thanks.

-amit

 

[Amit]

Yes once you join the pristine system.mdw workgroup, you'll no longer get a
login prompt.

If you still are getting a login prompt, then a password has been set for
the Admin user in that workgroup.

I joined the other system.mdw file (C:\WINDOWS\system32\), restarted my
computer, and am still getting a Logon prompt. So, seems like the password
for the Admin user has been set.

Will copying the system.mdw file from another user solve this?
Will deleting the system.mdw file and restaring my computer work?

Thanks.

-amit

 

[Joan Wild]

How can I unset the password? Will deleting both the "system.mdw"
files and re-starting my computer somehow regenerate the original
"system.mdw" file? I remember reading that in the ng somewhere.

I would rename them instead of deleting. You don't need to restart your
computer. Instead just start Access (it should create a new system.mdw for
you, but it depends on version). If you are using 97 (and maybe 2000), then
you could copy system.mdw from another computer.

Will deleting the new file ("TESTSYSTEM.MDW") undo this?

No! That could leave you with no way of getting into your mdb.

Your website mentions that in the
final steps, creating a short-cut will ensure that I am joined to the
standard system.mdw for all sessions of Access (for other unsecured
databases).

I does not say that. Creating a shortcut doesn't mean that you are joined
to system.mdw. What it says is to use the workgroup administrator to rejoin
system.mdw, and then create a shortcut to launch your secure mdb.

 

[Amit]

Thanks Joan.

I would rename them instead of deleting. You don't need to restart your
computer. Instead just start Access (it should create a new system.mdw for
you, but it depends on version). If you are using 97 (and maybe 2000), then
you could copy system.mdw from another computer.

I re-named the system.mdw, and opened Access (ver 2000). After opening
Access, I tried to open a db file, and I got a message "An error occured and
this feature is no longer working properly. Would you like to repair this
feature now?"
When I click "No", it says "MS Access could not find System.mdw. This file
is required for startup.".

Should I go ahead and click "Yes"?

I does not say that. Creating a shortcut doesn't mean that you are joined
to system.mdw. What it says is to use the workgroup administrator to rejoin
system.mdw, and then create a shortcut to launch your secure mdb.

Yes, I agree. And, thanks for being exact. I was just quoting the words from
that section. I intend to follow all the steps in that section.

-amit

 

[Joan Wild]

I would copy system.mdw from another computer.

If that fails, then yes try a repair. It should work by copying system.mdw
from another computer that doesn't prompt for username/password.

 

[Amit]

I would copy system.mdw from another computer.

If that fails, then yes try a repair. It should work by copying system.mdw
from another computer that doesn't prompt for username/password.

Joan,

Thanks for your response.

I've been giving this some thought, and was wondering if I delete the user
"amit" and clear the password for "Admin", that should also take care of this
issue.

Since, somehow, I created the new user, and set the password for "Admin" in
system.mdw, taking the above steps should stop Access from giving a Logon
window when I open any database (as it is doing now).

Thouhgts?

-amit

 

[TC]

Some (all?) versions of Access recreate the default workgroup file if
it is not present. So, if you are currently joined to the default file,
just close Access; rename the default file to something else; start
Access (from Runrograms), & see what happens.

One way or the other, it's easy to restore a default workgroup file
that does not ask for a password. You could reinstall Access, or copy
the default file from another PC, and so on. The question is, whether
you can still /access/ all of your databases, using the new default
file. Since I have not followed all of this thread, I can not comment
on that, one way or the other.

If there is any doubt as to whether you will be able to access all of
your databases using a restored default file, you should make sure to
save all the existing workgroup files on your PC. Maybe rename them to
..bak's, instead of deleting them. Then, if the restored default file
does not let you access all of your databases, at least you still have
the previous workgroup files, to try something else.

HTH,
TC

 

[Joan Wild]

I've been giving this some thought, and was wondering if I delete the
user "amit" and clear the password for "Admin", that should also take
care of this issue.

As long as you are talking about the correct workgroup file. You don't want
to do this in a workgroup that you used to secure your database. Ensure you
do this in the standard system.mdw that ships with Access (and also put
Admin in the Admins Group)

 

[Amit]

As long as you are talking about the correct workgroup file. You don't want
to do this in a workgroup that you used to secure your database. Ensure you
do this in the standard system.mdw that ships with Access (and also put
Admin in the Admins Group)

Thanks, Joan.

I was able to delete the user, and clear the password. Now, I'm able to open
all databases without the logon prompt.

Thanks for your patience and posts to guide me through.

-Amit