FIX: Can't Set Property on Interface That Has Attached Root

Last reviewed: December 1, 1997
Article ID: Q171538

The information in this article applies to:

Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0
Microsoft Visual Studio 97

SYMPTOMS

The Repository will allow you to add an interface to the root object that has both a property and a relationship. The Repository won't have problems if you add a new relationship to the relationship collection. However, it won't allow you to set the property.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 3.

For more information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q170365
   TITLE     : INFO: Visual Studio 97 Service Packs - What, Where, and Why

For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 3, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q175450
   TITLE     : INFO: Visual Basic 5.0 Fixes in Visual Studio 97
               Service Pack 3

MORE INFORMATION

Steps to Reproduce Problem

Create an interface that has both a property and relationship.
Retrieve the root object's class object and add the interface.
Try to set a property from that interface after the TIM has been fully created.
Note that in Visual Basic, an "Automation Error" occurs.
In Visual C++, the following error message is returned:
```
      "Can't set property on repository TIM objects"
```

Keywords          : VS97FixlistSP3
Version           : WINDOWS:5.0; WINNT:97
Platform          : WINDOWS winnt
Issue type        : kbbug
Solution Type     : kbfix kbservicepack

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

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