RE: security wizard cannot be run

OK - this goes from bad to worse...

From what you said I understood that I need to assign the Admin user a
password. I tried to log on as Admin but couldn't get in to the database, so
I looged in as the user with full permissions and cleared the Admin users
password with the intention of going back into the database and setting a new
Admin users password. As a result Access won't let me even open the database.
What do I do now? Panic is starting to set in!

"Joan Wild" wrote:


"Desperate!!" wrote:

Thanks Joan, but the more I practise the more confused I get. I've tried
linking to a system.mdw and it won't let me reopen the database.

That's actually a good sign. You shouldn't be able to open a secure
database while joined to the system.mdw.


Using the secure.mdw I've been able to work out how to reactivate users
passwords, and all seemed to be going swimmingly until I tried to open the
database (which sits in a shared area on a network) from another user account
on the same PC and there was no request for passwords!!!

The login dialog will pop up only if you set a password for the Admin user.

That makes access security the brightest thing since george W. Bush, so I'm
sure I'm doing something fundamentally wrong. Why does the security only seem
to apply to a particular users software rather than the database itself?

Security permissions are stored in the mdb file. Usernames/groups/passwords
are stored in the secure mdw file. As long as the Admin user in that mdw
file has a password set, then you'll get a login prompt. Then the user must
log in using a valid username/password. Once the database opens, the
permissions on the objects in the mdb determine whether this user can
open/edit/etc. that object.

So create a desktop shortcut to open your mdb. The target will have the
following in it.
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"
substituting the correct paths of course.

Use that shortcut to open the mdb as a user that has full permissions to
everything (this would be the user you put into the Admins Group). This user
should have all permissions, and they are able to assign permissions to other
users, etc.

--
Joan Wild
Microsoft Access MVP


.

Relevant Pages

  • Re: Probs accessing database for users of newly developed Superuse
    ... but the SuperUsers cannot get into it. ... You've double-checked their permissions and all are correct. ... I've included the code for when the form opens below. ... ' Minimize the database window and initialize the form. ...
    (microsoft.public.access.security)
  • Re: Probs accessing database for users of newly developed Superuse
    ... but the SuperUsers cannot get into it. ... double-checked their permissions and all are correct. ... I've included the code for when the form opens below. ... ' Minimize the database window and initialize the form. ...
    (microsoft.public.access.security)
  • Re: User Level Security Malfunction
    ... menu, the Users group has no rights to open the database, and it also ... I first create a blank secured file that I ... Remove Admin from Admins group ... Remove all permissions to "new" objects from Admin ...
    (microsoft.public.access.security)
  • Re: Issue: LDB Not Being Created
    ... I would totally agree that it is a rights issue (and was convinced it ... I open the database and the LDB gets created. ... file create permissions, then all other users of the network would be able ... However if one user opens up the file does not have correct permissions to ...
    (comp.databases.ms-access)
  • Q: low permission cannot convert from A97 to A2000/2003
    ... A97, but the database is sent out and used by contractors (user permissions) ... The admin user has full privileges. ... The problem we are having is converting the database from A97 to 2000+. ...
    (microsoft.public.access.security)
Loading