FIX: Using Set for ListItem's SubItem Results in GPFLast reviewed: December 18, 1997Article ID: Q171577 |
The information in this article applies to:
SYMPTOMSUsing the Set keyword when setting the value of a ListItem's SubItem results in a General Protection Fault.
CAUSEThe SubItems collection of the ListItem is designed to handle strings, not objects.
RESOLUTIONDo not use the Set keyword. Instead of code similar to:
Set ListItem.SubItems(1) = Text1use the following code:
ListItem.SubItems(1) = Text1where Text1 is a textbox object.
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 2. For more information on the Visual Studio 97 Service Pack 2, 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 2, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q171554 TITLE : INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2 MORE INFORMATIONAlthough the code listed above that uses the Set keyword is incorrect, it should not result in a General Protection Fault. Once the Visual Studio 97 Service Pack 2 is installed, the Visual Basic correctly raises the "Type Mismatch" error. Keywords : vb5all VS97FixlistSP3 VS97FixlistSP2 VB5FixlistSP2 Version : 5.0 Platform : NT WINDOWS Issue type : kbbug Solution Type : kbfix kbservicepack |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |