Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Difference between revisions of "Microsoft KB Archive/171525"

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 47: Line 47:
 
== SYMPTOMS ==
 
== SYMPTOMS ==
  
When viewing the information on the "Column Headers" tab of the custom property sheet for a ListView control, you may receive an error similar to the following:
+
When viewing the information on the "Column Headers" tab of the custom property sheet for a ListView control, you may receive an error similar to the following:
 
<div class="errormessage">
 
<div class="errormessage">
  
&quot;VB5 caused an invalid page fault in module COMCTL32.OCX at 0137:202d3d20&quot;
+
"VB5 caused an invalid page fault in module COMCTL32.OCX at 0137:202d3d20"
  
 
</div>
 
</div>

Latest revision as of 11:05, 21 July 2020

Knowledge Base


FIX: ListView Causes IPF When Accessing ColumnHeaders Property

Article ID: 171525

Article Last Modified on 12/10/2003



APPLIES TO

  • Microsoft Visual Basic 5.0 Control Creation Edition
  • Microsoft Visual Basic 5.0 Learning Edition
  • Microsoft Visual Basic 5.0 Professional Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition



This article was previously published under Q171525

SYMPTOMS

When viewing the information on the "Column Headers" tab of the custom property sheet for a ListView control, you may receive an error similar to the following:

"VB5 caused an invalid page fault in module COMCTL32.OCX at 0137:202d3d20"

CAUSE

This problem occurs with version 5.00.3828 of COMCTL32.OCX. The version of this control that ships with Visual Basic 5.0 (version 5.00.3714) does not exhibit this problem.

RESOLUTION

Upgrade to Visual Studio 97 Service Pack 2. The updated version of the COMCTL32.OCX installed by Service Pack 2 corrects this problem.

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. For more information on the Visual Studio 97 Service Pack 2, 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 2, please see the following article in the Microsoft Knowledge Base:

171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2


Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171525