The information in this article applies to:
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.
CAUSEMicrosoft 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. RESOLUTIONVerify 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. STATUSThis behavior is by design. MORE INFORMATIONSteps to Reproduce Behavior
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/ Additional query words:
Keywords : kbinterop kbSQLServ kbVisDBTools kbVisID100 kbVisID600 kbGrpASP VIServer kbDtDbDesigner |
Last Reviewed: November 8, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |