Re: Able to open secured database with default MDW

Well, here's what I found. If I used the Security Wizard, I was able to open
the database when joined to Syst em.mdw. Finally, after three tries, I
decided to give up on the Wizard and do everything manually (a note in step
10 of Lynn Trapp's instructions gave me the idea). That worked! My database
is now only accessible with my custom mdw.

--susan


"Susan L" wrote:

Joan and David: I want to thank you both for your efforts to help me. It
seems the impossible is happening, so I think I need to go back and start
from scratch, following your (Joan's) instructions precisely. I must have had
some sort of lapse -- as David mentioned. Just to close the loop, I'll post
back once I get it working properly. Thank you again.
--
susan


"david epsom dot com dot au" wrote:

Just a point: the admin user is in /this/ Users group /here/.

The admin user can be (and is) in any other group in any other
workgroup.

In particular, the admin user is in the Admins group in most
default system.mdw files.

The question is not if this Users group has any permission:
the question is if any of the groups in your default system.mdw
have any permissions.

On your description, there is a group or user in your default
system workgroup that does have permission.

There is a small chance that you have accidentally created
a secured workgroup where the Admins group is identical to
your default Admins group. (by making the wrong choices for
the security strings).

For myself, it is more common to have a lapse of concentration
at a critical point, and do something wrong, like use the
wrong workgroup, or the wrong login, or use a copy of the
default workgroup, or whatever.

(david)


"Susan L" <SusanL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BE701EFB-E40C-4870-ABD1-2810108E4287@xxxxxxxxxxxxxxxx
Joan: I logged on as sradmin and confirmed that the database and all
objects
were owned by that user. The admin user is in the Users group -- and I
confirmed that this group has no privileges on anything. Then typed what
you
suggested in the immediate window -- and my custom workgroup appeared in
response.

All this and I can still get into the database directly when using
System.mdw. I really am puzzled.
--
susan


"Joan Wild" wrote:

When you open your secure database, are you logging in as sradmin? If
so,
then you can go to Tools, Security, Permissions and verify that the Admin
User and the Users Group have NO permissions on anything. You can also
go
to the Change Owner tab, and verify that sradmin does indeed own
everything.

You may not need to start over.

Also once you log in, hit Ctrl-G and type
?DBEngine.SystemDB
That should tell you for certain, what mdw file you are currently using.


--
Joan Wild
Microsoft Access MVP

Susan L wrote:
I'm pretty sure I was. Could my user "sradmin" be the owner of the
database and all objects if I were't in the custom workgroup file
when I created the new database? Do you think I need to start all
over? --
susan


"Joan Wild" wrote:

Hi Susan,

You missed a step somewhere.

Are you sure you were joined to your secure mdw when you added the
user? You may have still be joined to system.mdw.


--
Joan Wild
Microsoft Access MVP


"Susan L" wrote:

I've searched the newsgroups on this topic and have come up with
answers that I have already addressed. The problem is that I am
able to open my "secured" file when using the default System.mdw.
(I'm using Access 2003) Plus, I followed Joan Wild's and Lynn
Trapps instructions closely. Maybe there's something I've
overlooked? 1) Created custom workgroup file, with a custom admin
user, "sradmin." 2) Logged on as SR admin & created password.
3) Logged on again as sradmin and created blank database into which
I imported all objects.
4) Verified that sradmin owns all objects including the database
itself. 5) Verified that the Users group has no privileges.
6) Moved the Admin user to the Users group.
7) Created shortcut for opening the secured database.

When I set up security before (Access 2000), whenever I double
clicked the database icon, I received a "no privileges" message.
The only way to get in was to use the shortcut. I originally
thought it might be my copy of Access at work, but the same thing
is happening on my home computer (Access 2003). Any suggestions?
--
susan






.

Relevant Pages

  • Re: Access Security not secure
    ... The first step is to create a new workgroup. ... > I created the Administrator and added him to the admin ... > No luck if I try to open the database from a computer that> is attached to the default workgroup I have full access to> the entire database. ... >>Should secure your database enough. ...
    (microsoft.public.access.security)
  • Re: Access Security not secure
    ... You should secure it manually. ... > In your test with using a new workgroup and running the> wizard it was in access2000 then again in access2002 ... >>> to work well until I try to access the database on the ... >>>>> I created the Administrator and added him to the> admin ...
    (microsoft.public.access.security)
  • Re: Able to open secured database with default MDW
    ... Joan and David: I want to thank you both for your efforts to help me. ... The admin user can be in any other group in any other ... system workgroup that does have permission. ... All this and I can still get into the database directly when using ...
    (microsoft.public.access.security)
  • Re: Able to open secured database with default MDW
    ... The admin user can be in any other group in any other ... system workgroup that does have permission. ... All this and I can still get into the database directly when using ... "Joan Wild" wrote: ...
    (microsoft.public.access.security)
  • Re: Sorting out security
    ... There is a link to it on the Security page of my website. ... > files and remote logins to a secured database. ... different name for the secure workgroup file. ... If the Admin user has no password then every user is ...
    (microsoft.public.access.security)