Yes, you obviously missed a step, since with a correctly secured database you would not be able to log in with a
different workgoup.

I suggest using the .bak file (which is basically your original file) and trying this again, expect using either (a) the
Security wizard to do the entire security process or (b) doing the entire process yourself by following Joan Wild's
process: http://www.jmwild.com/Accesssecurity.htm (see the step by step instructions). Don't forget to make a copy of
your file first, just in case.

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

At this stage, you should be able to logon as (say)(a user who you say should
not have permissions)(or any other way probably), and go through the User and
Group permissions and FIND OUT which user or group has such permissions when
they should not have. Starting with Database Permissions and going through
other objects as well.

One of the criticisms of Security Wizard, apart from potential bugs in the
wizard vs ULS (which may or may not be true), is that it shields you from a
full understanding of ULS. I believe, in the longer term, you MUST be capable
of going through the users and groups, and many objects of course, to see
where an errant permission lies. One school of thought, is that "wizards" just
try to hide this understanding from you!

The obvious thing, is that NO permissions should be assigned to any standard
user or group supplied in a default Access program.

I agree that some "step" must have been missed. And that the SecFAQ seems to
list the Sec Wizard as a step. But I do not agree that the Wizard should be
used at all!!! (for evidence, your own post)

HTH
Chris

(I have never used the security wizard, probably because I didn't know about
it when I started!)

(for a free alternate security analyser, same info as in-built but arguably
more presentable, see this tool -which is nothing to do with me- :
http://www.grahamwideman.com/gw/tech/access/permexpl/index.htm

) (closing bracket)