ACC1x: User with Full Permissions Cannot Run Query

Last reviewed: May 14, 1997
Article ID: Q96102
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SYMPTOMS

You receive the following message even though you have full permission on a table:

   Couldn't read; no read permission for table or query <query name>

You can view the table in Datasheet and Design view, and you can open the query in Design view.

CAUSE

This occurs when a query has the property Run With Owner's Permissions checked and the user who created the query (the owner) is no longer on the system. Either the owner was deleted or the database was opened in a Microsoft Access session that was started with a different SYSTEM.MDA where the owner is not a included.

When the property Run with Owner's Permissions is checked, Microsoft Access checks the owner's permissions. It does not compare the owner's permissions to those of the user running the query. Therefore, if the owner is not on the system, other users cannot execute the query as long as the property Run with Owner's Permissions is checked.

RESOLUTION

To allow users to run the query with their own permissions, clear the Run With Owner's Permissions check box and save the query.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access versions 1.0 and 1.1. This problem no longer occurs in Microsoft Access version 2.0.

MORE INFORMATION

Steps to Reproduce Problem

  1. Start Microsoft Access. If you have activated security, log in as a member of the group Admins.

  2. From the Security menu, choose Users.

  3. Press the New button and add a new user called John. Add another user called Jane. Do not assign either to any group other than Users.

  4. If you have already activated security, skip this step. Choose Change Password... from the Security menu. Leave the Old Password blank, enter Admin for New Password and Verify. Press the OK button.

  5. Exit and restart Microsoft Access. Log in as John leaving the password blank.

  6. Create a new query based on any table. If you are in a secure system, base the query on a table that the Users group has full permissions to. From the View menu, choose Query Properties and select the Run with Owner's Permissions check box.

  7. Exit and restart Microsoft Access. Log in as Admin using the password Admin.

  8. Choose Users from the Security menu. Delete the user John.

  9. Exit and restart Microsoft Access. Log in as Jane leaving the password blank.

  10. Attempt to run the query.

    At this point, you will see the error message "Couldn't read; no read permission for table or query '<query name>'.

  11. Verify that Jane can open the query in Design view as well as open the table on which the query is based.

To avoid the problem, in Design view, the user Jane can choose Options from the View menu and clear the Run With Owner's Permissions check box. Depending on the security, that may have to be done by an Admin. After you clear the check box, the query will run.

REFERENCES

For more information on query permissions, search for "Run with Owner's Permissions" using the Microsoft Access Help menu.


Additional query words: serial number pin ADK
Keywords : kberrmsg kbusage ScrtOthr
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : kbworkaround


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 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.