The information in this article applies to:
SYMPTOMSWhile 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. RESOLUTIONA 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. Q170365 INFO: Visual Studio 97 Service Packs - What, Where, and WhyFor 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: Q171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2 MORE INFORMATIONSteps to Reproduce Behavior
allowedtypes is recognized.Actual Results: Interface IVcmGroup is recognized but none of its relationship collections (including allowedtypes) is recognized. Additional query words:
Keywords : kbVBp500 kbVS97sp2fix kbGrpVBDB kbvbp500sp2fix |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |