ACC2: Permissions Command Unavailable When Logged in As Guest

Last reviewed: May 28, 1997
Article ID: Q115572
The information in this article applies to:
  • Microsoft Access version 2.0

SYMPTOMS

Advanced: Requires expert coding, interoperability, and multiuser skills.

When you log into Microsoft Access as Guest (when Guest is assigned the default permissions) and then create a database, you cannot view or change permissions on any of the objects in the database.

CAUSE

The Permissions command is always unavailable when you are logged in as Guest, even if you give the Guest user permissions to view or change object permissions.

This behavior occurs because the Guests group does not inherit read data permission on the MSysUserList query in the SYSTEM.MDA file. To prevent permission-related errors, the Permissions command is always disabled for users logged in as Guest.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Start Microsoft Access and open any database.

  2. Enable security (if it is not already enabled) by assigning a password to the Admin user. To do this, choose Change Password from the Security menu, and then enter a password for the Admin user (the Admin user is the default user).

  3. Quit Microsoft Access and then restart it. Log in as Guest (no password required).

  4. Create a new database.

  5. Create a new table, and then create a query based on the table.

  6. From the Security menu, try to choose Permissions. Note that the Permissions command is unavailable.


Additional query words: security greyed grayed
Keywords : kbusage ScrtPerm
Version : 2.0
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.