Re: Able to open secured database with default MDW

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: Sorting out security
    ... > MS Access security. ... > created a new workgroup, added a password for the Admin role, added ... > remote logins to a secured database. ... The location of the current workgroup file is recorded in the ...
    (microsoft.public.access.security)
  • Re: user level security wizard
    ... the name of the database in this shortcut was not the copy, ... But the error message you got I thought was in reference to the mdw file, ... you said that every mdw file has the admin user and the Users Group ... and the security wizard does this for you. ...
    (microsoft.public.access.security)
  • Sorting out security
    ... MS Access security. ... created a new workgroup, added a password for the Admin role, added groups, ... user IDs and passwords for users and allocated permissions on the ... remote logins to a secured database. ...
    (microsoft.public.access.security)
  • Re: Help - Pathworks & Windows 2000 Advanced Server
    ... Your privilege level on domain TURPINS-WM is ADMIN. ... The partial synchronization replication of the LSA database from the ...
    (comp.os.vms)
  • Re: Problems setting up access security
    ... The Admin user still owns the database object. ... You secured it using the system.mdw, thinking that you were using your secure mdw. ...
    (microsoft.public.access.security)