BUG: Database Object Permissions Overwritten in SQL Ent. Mgr.

 Last reviewed: December 11, 1997
Article ID: Q166682
The information in this article applies to:
  • Microsoft Visual InterDev, version 1.0

SYMPTOMS

Any permission changes made using SQL Enterprise Manager, or similar tools, while a database object is open in the Visual InterDev Source Editor is overwritten when the object is saved from within Visual InterDev.

This applies to developers and users that have SQL Server or Oracle dataconnections.

CAUSE

Microsoft Visual Database Tools checks permissions on a object at the time that the object is loaded into the Source Editor. When the object is saved, those permissions are not rechecked. Visual InterDev saves the database objects with the same permissions with which it was opened. This behavior overwrites any changes that have occurred since the object was opened.

RESOLUTION

Verify that the object is not open in a Visual InterDev Source Editor when the permissions are being changed. Alternatively, do not change permissions on an object that is open in the Visual InterDev Source Editor.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Launch Visual InterDev and SQL Enterprise Manager.

  2. Create a project in Visual InterDev and add a SQL dataconnection.

  3. Open a stored procedure from the dataconnection into the Source Editor.

  4. Using SQL Enterprise Manager, change the permissions on the stored procedure that is open.

  5. In Visual InterDev, save the stored procedure.

The permission changes made in SQL Enterprise Manager are lost. The Stored Procedure permissions revert back to those it had when the procedure was opened into the Source Editor.

NOTE: To verify in the SQL Enterprise Manager that the permissions are indeed the same as those when the procedure was opened in the Visual InterDev, right-click the "Stored Procedures" folder in the SQL Enterprise Manager and select Refresh from the shortcut menu.

REFERENCES

For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site: 

   http://support.microsoft.com/support/vinterdev/


Keywords          : kbDtDbDesigner VIServer kbinterop kbbuglist
Version           : 1.0
Platform          : WINDOWS
Issue type        : kbbug

================================================================================

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