Article ID: 171811
Article Last Modified on 10/28/2003
APPLIES TO
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
This article was previously published under Q171811
SYMPTOMS
While attempting to use the allowedtypes relationship collection of the IVcmGroup interface in the AddDefaultData function of the Visual Component Manager, the relationship collection is not recognized. However, this interface can be seen from the Browser and is, in almost all ways, identical to all other interfaces in this and other types of information models. The difference is that when this interface was created, the TableName was set to the empty string. When the TableName is set to an actual table, the allowedtypes relationship collection becomes recognized and there is no problem.
RESOLUTION
A workaround to this behavior would be to apply an "explicit" TableName.
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 2.
For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
170365 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 2, please see the following article in the Microsoft Knowledge Base:
171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2
MORE INFORMATION
Steps to Reproduce Behavior
- Create the information model in a Repository with the UML, DTM, and CDE models in it.
- Place the Repostry.mdb in the windows\msapps\repostry directory.
- Launch Visual Component Manager or a custom app that uses the allowedtypes relationship collection.
Expected Results:
allowedtypes is recognized.
Actual Results:
Interface IVcmGroup is recognized but none of its relationship collections (including allowedtypes) is recognized.
Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171811
