FIX: Bad Error Number Returned if Relationship Doesn't Exist (171537)


The information in this article applies to:

  • Microsoft Visual Basic Professional Edition for Windows 5.0
  • Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q171537

SYMPTOMS

When you use the OLE Automation interface, an invalid error number is returned if a relationship that doesn't exist is requested.

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:

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 3, please see the following article in the Microsoft Knowledge Base:

175450 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 3

MORE INFORMATION

Steps to Reproduce Behavior

Use the Item method to attempt to retrieve a relationship that doesn't exist.

Expected: EREP_RELSHIP_NOTFOUND should be returned.

Results: The correct error description is returned but with an invalid error number (0x80020009).
Modification Type:MajorLast Reviewed:11/5/2003
Keywords:kbbug kbfix kbVS97sp2fix KB171537
©2003 Microsoft Corporation. All rights reserved.