ACC: Can Change 1.x Object Ownership w/ DAO in Later Versions

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

SYMPTOMS

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

You can use data access objects (DAO) in Microsoft Access versions 2.0, 7.0, and 97 to change the ownership of database objects (such as tables, forms, and reports) in unprotected Microsoft Access version 1.x databases, even though you cannot view or change the ownership of these objects using Microsoft Access version 1.x.

CAUSE

Although there is no command to change object ownership in Microsoft Access 1.x, the underlying Microsoft Jet database engine does support changing ownership. The method of changing object ownership in Microsoft Access 2.0, 7.0, and 97 works on both version 1.x and version 2.0 databases.

RESOLUTION

To keep ownership of objects in your version 1.x database from being changed, protect the database with the Microsoft Access version 1.x Security Wizard.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access 2.0, 7.0, and 97. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

REFERENCES

For more information about database ownership, search the Help Index for "Owner," or ask the Microsoft Access 97 Office Assistant.


Keywords : kbusage ScrtOwnr
Version : 1.0 1.1 2.0 7.0 97
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.