User and Workgroup was screwed

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Aki - 23 Jul 2006 07:38 GMT

Hi
We have a Access database for logging all the activities we do everyday. It
was oreginally created and designed by one of my co-workers. Just about few
days ago, he tried to add a person onto the user list for giving permission
to edit some of the tables. However, somehow the whole system was screwed
and now it won't let us in and shows message says that we don't have the
administrative right. It now doesn't shows up any login window. We have
done anything we can do tried to fix the problem, even replace the .mdw
file, but still no luck.

Is there anyone can tell me what we can do to make the database to bypass or
remove the security setting? We've lost 19 days worth of log. It will be
appreciated if any one of you can help us with this trouble. Thanks.

Reply to this Message

Scott McDaniel - 23 Jul 2006 12:59 GMT

>Hi
>We have a Access database for logging all the activities we do everyday. It
[quoted text clipped - 9 lines]
>remove the security setting? We've lost 19 days worth of log. It will be
>appreciated if any one of you can help us with this trouble. Thanks.

If your db is properly secured Access must use the exact mdw file which was used when creating it, and if it can't find
that file it won't open. Did you make a copy of the file before you replaced it? If so, try moving the original back
into place.

How do you open the database? Do you use a shortcut, or doubleclick the file directly?

If you use a shortcut, right-click the shortcut and examine the Target property; it'll probably look something like
this:

"Full path to MSACCESS.EXE" "Full path to your db" /wrkgrp "Full path to your .mdw file"

Make sure the .mdw file is in the path specified.

If you don't use a shortcut to open your db, then the machine was probably "joined" to a workgroup. Open Access, then
click Tools - Security - Workgroup Administrator to see what workgroup you're currently joined to. Is that the correct
workgroup? If not, try re-joinnig the original workgroup.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

Reply to this Message

Aki - 25 Jul 2006 05:44 GMT

First, thank you for you response, Scott.

Unfortunately that my co-worker didnot keep a copy of the security.mdw or
system.mdw file after he implemented the security on the database. There is
a text file generated by Access after the implementation of security;
however, we tried to create a new mdw file by using those info in the text
file, but still no luck.

He told me that everything happened after he tried to add a new person and
password in the workgroup. After he clicked OK to accept the new setting
and restart the database, he can no longer open the file. It sounds to me
that he might have accidentally changed something about the administator
account, but only god knows what'd happened.

We have created a new copy of the database for current use. We run the
database on a monthly basis, which means we have lost "only" less than a
month of log, 19 days for exact. It may not sound a big deal. But, we are
a security department, and we are running the database as our daily activity
log, which logs almost everything. As I remember, until the time we lost
it, we already have about1400 records. It is actually a disaster for us.

If anyone can help me to at least get a copy of the main table out of the
database, it will be so appreciated.

Aki

>>Hi
>>We have a Access database for logging all the activities we do everyday.
[quoted text clipped - 41 lines]
> scott@takemeout_infotrakker.com
> www.infotrakker.com

Reply to this Message

Keith Wilby - 25 Jul 2006 08:06 GMT

Just a long shot, but try logging in as "Admin" with no password - it may be
that it wasn't secured properly in the first place but, as I say, it's a
long shot.

Keith.
www.keithwilby.com

Reply to this Message

Joan Wild - 25 Jul 2006 19:21 GMT

If Admin's password were blank, there would be no login dialog, thus no
opportunity to login.

Signature

Joan Wild
Microsoft Access MVP

> Just a long shot, but try logging in as "Admin" with no password - it
> may be that it wasn't secured properly in the first place but, as I
> say, it's a long shot.
>
> Keith.
> www.keithwilby.com

Reply to this Message

Aki - 26 Jul 2006 04:11 GMT

well, true enough. there is actually no chance for logging in. Once we
open the database, it shows warning message window on the screen and says
that we don't have administrator's right to access the file. Once we click
"OK", that's it, it stays closed.
I've tried many "password cracking" software, but no luck at all. it is not
about password, it is something else.

> If Admin's password were blank, there would be no login dialog, thus no
> opportunity to login.
[quoted text clipped - 5 lines]
>> Keith.
>> www.keithwilby.com

Reply to this Message

Joan Wild - 26 Jul 2006 13:05 GMT

As I understand it, your co-worker 'added a new user (and password)' - by
the way he likely didn't add a password if using the security dialogs as
that isn't possible. The PID is not a password.

Then you say 'the whole system was screwed' (which isn't too helpful). But
later messages you indicate that there is no login prompt at all.

If you are using the correct mdw file and get no login, then perhaps the
password was cleared for the Admin user. In that case, use the workgroup
administrator (Tools, security) to join by default to your secure mdw.
Close and reopen Access, and create a blank mdb. Go to Tools, security,
User accounts and click on the change password tab. Set a password for the
Admin user. Then use the workgorup administrator to rejoin the standard
system.mdw as your default.

Now try your desktop shortcut, and see if you can log in.

Signature

Joan Wild
Microsoft Access MVP

> well, true enough. there is actually no chance for logging in. Once
> we open the database, it shows warning message window on the screen
[quoted text clipped - 16 lines]
>>> Keith.
>>> www.keithwilby.com

Reply to this Message

Keith Wilby - 26 Jul 2006 08:09 GMT

> If Admin's password were blank, there would be no login dialog, thus no
> opportunity to login.

D'oh! Oh lord help me to keep my big mouth shut ...

Keith.

Reply to this Message