Re: User Level Security Malfunction

Are your users opening the same database as you? If your database is split, then you secured your copy of the frontend, but your users are still using their old (unsecured) frontend. You need to redistribute the new frontend.

If this isn't the case, then you missed a step in securing it, as Rick said.

--
Joan Wild
Microsoft Access MVP
"mikeycan" <mikeycan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:76032934-C70A-4778-BE5C-26C8B8831775@xxxxxxxxxxxxxxxx
Hello!

I have an Access 2003 database, and I ran the User Level Security Wizard on
the database, and it all seemed to work fine. I get prompted to log in and
the world is good. Later, I asked my other users to open the database, and
it let them all in, without prompting for a UserID/Password. I did a little
research and it suggested I might not have removed my Admin user from the
Admins group and/or not assigned a password to the Admin. But when I checked
the Users/Group Accounts and Users/Group Permissions, its shows that I
“successfully” made myself the owner of the database (different than the
Admin user), assign the Admin a password, and that the Admin user is not in
the Admins group. What could have gone wrong and how to I fix it? I have
done this before on an Access2000 database had had no issues.

The same articles also recommended that I create a new blank database with a
new workgroup (manually) and import the old database objects. I got to the
point of trying to import, then I got the error that I don’t have permissions
from the old database. I logged into the old database (hoping if I had both
open it would work) and it still gives me the same error on import.

.

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)