ACC: Can't Change Ownership When RunPermissions Set to Owner's

Last reviewed: May 7, 1997
Article ID: Q120885
The information in this article applies to:
  • Microsoft Access versions 2.0, 7.0, 97

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

The owner of a query cannot transfer its ownership if the query's RunPermissions property is set to Owner's. This is true even if the owner has Administer permission for the query.

RESOLUTION

Change the query's RunPermissions property from Owner's to User's. Then you can change the ownership of the query.

STATUS

This behavior is by design. Allowing someone to change the ownership of the query after the RunPermissions property has been set to Owner's would be a security breach.

MORE INFORMATION

To change the ownership of a database object, you must have Administer permission for the object. You can change your permissions on the object if you are logged on as the object's owner, as a member of a group that has Administer permission on the object, or as a member of the Admins group in the workgroup in which the database that contains the object was created. If you cannot change your permissions on an object, see your workgroup administrator or the object's owner.

NOTE: Even if you satisfy all conditions in the previous paragraph, you still cannot transfer ownership of a query if its RunPermissions property is set to Owner's.

Steps to Reproduce Behavior in Microsoft Access 7.0 and 97

  1. Start Microsoft Access and log on as the Admin user.

  2. Open the sample database Northwind.mdb, and then open the Current Product List query in Design view.

  3. Using the right mouse button, click the query and then click Properties on the menu that appears. Set the query's RunPermissions property to Owner's, and then save and close the query.

  4. On the Tools menu, point to Security, and click User and Group Accounts. Click the New button and create a new user called Joe, and make him a member of the Users group. Click OK.

  5. On the Tools menu, point to Security, and click User and Group Permissions. Click the Change Owner tab.

  6. In the Object Type box click Query, and select the Current Product List query in the Object box. In the New Owner box, select Joe. Click the Change Owner button. Note that you receive the message:

          You don't have permission to change the owner of 'Current Product
          List.'
    

Steps to Reproduce Behavior in Microsoft Access 2.0

  1. Start Microsoft Access and log on as the Admin user.

  2. Open the sample database NWIND.MDB, and then open the Catalog query in Design view.

  3. Using the right mouse button, click the query and then click Properties on the menu that appears. Set the query's RunPermissions property to Owner's, and then save and close the query.

  4. On the Security menu, click Users. Click the New button and create a new user called Joe, and make him a member of the Users group. Click Close.

  5. On the Security menu, click Change Owner.

  6. In the Object box, select the Catalog query. In the New Owner box, select Joe. Click the Change Owner button. Note that you receive the message:

          You don't have permission to change the owner of 'Catalog'.
    

REFERENCES

For more information about RunPermissions, search the Help Index for "RunPermissions."


Keywords : kberrmsg kbusage ScrtOwnr
Version : 2.0 7.0 97
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 7, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.