DOCUMENT:Q171544  01-DEC-1997  [vbwin]
TITLE   :FIX: Engine: Collection Object Doesn't Access Correctly by Name
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:5.0; WINNT:97
OPER/SYS:WINDOWS winnt
KEYWORDS:VS97FixlistSP3 VB5FixListSP3

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

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

SYMPTOMS
========

If 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")

CAUSE
=====

If 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.

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
======================================================================
Keywords          : VS97FixlistSP3 VB5FixListSP3
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.

Copyright Microsoft Corporation 1997.