RE: security wizard cannot be run


"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: User access on a company intranet
    ... Yes they need full permissions on the folder where the backend is. ... You wouldn't need to do this in your copy of the database. ... However you can toggle the shiftkey bypass from another mdb file. ... When you want to implement security, you create a new mdw file, ...
    (microsoft.public.access.security)
  • 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: Adding new users to an Access 2002 DB
    ... So the mdb opens when you are using the standard system.mdw. ... It sounds like someone didn't secure it properly, ... When you open it, go to Tools, Security, permissions and check to see what ...
    (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: Access to Access Automatic Updates
    ... Then navigate to the database from the File Open dialog and open it. ... You will need to do it for mdb that has tables you need ... MS Office Master 2000 ed. ... you will need to create a form that opens on ...
    (microsoft.public.access.externaldata)
Loading