Interesting "Locked In" Problem

[tbl]

How can I "force" a login dialog, without blowing away the
special MDW file? I've removed the user "Admin" from the
Admins group (dumb mistake, I now realize), but Admin still
has "Full Data" membership, and the mdb opens without
offering a login dialog. I can get another co-worker to log
in with their Admins membership, if I could just get a login
dialog to come up!

 

[Rick Brandt]

How can I "force" a login dialog, without blowing away the
special MDW file? I've removed the user "Admin" from the
Admins group (dumb mistake, I now realize), but Admin still
has "Full Data" membership, and the mdb opens without
offering a login dialog. I can get another co-worker to log
in with their Admins membership, if I could just get a login
dialog to come up!

Access security is hard (at first) and the vast majority of people who try to
secure a file fail to do so correctly. You are in the lucky segment of that
group because you realized that your file is not secured properly. (Most files
that people think are secured properly are not).

You cannot hope to get this right by playing around with the help file and the
wizard. Google this group for "FAQ + step by step instructions". There are a
handful of web sites that offer very explicit instructions that when followed
exactly will result not only in a properly secured file, but in teaching you how
all of it works as well.

By the way, the Admin users should be removed from the Admins group. The most
common mistake is that people leave Admin as the owner of the database and
owners can open files even if they don't have "permissions" to do so.

 

[tbl]

Access security is hard (at first) and the vast majority of people who try to
secure a file fail to do so correctly. You are in the lucky segment of that
group because you realized that your file is not secured properly. (Most files
that people think are secured properly are not).

You cannot hope to get this right by playing around with the help file and the
wizard. Google this group for "FAQ + step by step instructions". There are a
handful of web sites that offer very explicit instructions that when followed
exactly will result not only in a properly secured file, but in teaching you how
all of it works as well.

By the way, the Admin users should be removed from the Admins group. The most
common mistake is that people leave Admin as the owner of the database and
owners can open files even if they don't have "permissions" to do so.

Thanks Rick--I'm on it!

 

[Geoff]

Following on from Rick's tip, you might find the following article helpful:

http://support.microsoft.com/kb/289885/

Regards
Geoff

 

[Joan Wild]

Following on from Rick's tip, you might find the following article
helpful:
http://support.microsoft.com/kb/289885/

That article is wrong. It has you setting a password for the Admin user in
system.mdw, rather than in the new mdw you created. One is better off
following the steps in the security FAQ.

 

[Geoff]

Joan: Yes - I see what you mean.

If only they'd left out "(system.mdw)" in paragraph 2 and had said "and give
the new workgroup file a different name" (which it defaults to anyway)...

Otherwise, it seems a concise step-by-step procedure. (I only mentioned it
as it went on to talk about removing permissions from the Users group, which
hadn't yet been mentioned in this conversation).

It's surprising the article hasn't been updated, given the consequences of
putting a password on the system.mdw.

Geoff