FIX: Engine: Collection Object Doesn't Access Correctly by NameLast reviewed: December 1, 1997Article ID: Q171544 |
The information in this article applies to:
SYMPTOMSIf you create a Naming relationship on an object and you add an instance such as:
x.add Obj,"12"you cannot access this object by name, such as:
set y = x("12") CAUSEIf you use a string that can be evaluated as a number (such as [ASCII 147]12[ASCII 148]) for the name of an object in a naming relationship, you cannot access that object by that name. The reason is that the repository evaluates any string that could be a number as an index rather than a name.
STATUSMicrosoft 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 WhyFor 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 Keywords : VS97FixlistSP3 VB5FixListSP3 Version : WINDOWS:5.0; WINNT:97 Platform : WINDOWS winnt Issue type : kbbug Solution Type : kbfix kbservicepack |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |