Microsoft KB Archive/198605

= BUG: Find Next Crashes After Closing a Maximized Code Window =

Article ID: 198605

Article Last Modified on 5/13/2003

-

APPLIES TO


 * Microsoft Visual Basic 5.0 Learning Edition
 * Microsoft Visual Basic 6.0 Learning Edition
 * Microsoft Visual Basic 5.0 Professional Edition
 * Microsoft Visual Basic 6.0 Professional Edition
 * Microsoft Visual Basic 5.0 Enterprise Edition
 * Microsoft Visual Basic 6.0 Enterprise Edition

-



This article was previously published under Q198605



SYMPTOMS
Closing a maximized code window after performing a Find and Find Next subsequently on the code window causes Visual Basic to crash.

The possible error messages are:

An application error has occurred.

VB6.exe

Exception: Access Violation (0x00000005) Address: 0x0fb16e90

-or-

An application error has occurred.

VB5.exe

Exception: Access Violation (0x00000005) Address: 0x0fb16e90

-or-

This program has performed an illegal operation and will be shut down.

-or-

Edit: VB6.EXE Application Error

The instruction at "0x0fa76bb1" referenced memory at "0x00000058". The

memory could not be "read".

-or-

Edit: VB5.EXE Application Error

The instruction at "0x0fa76bb1" referenced memory at "0x00000058". The

memory could not be "read".



RESOLUTION
This problem does not occur if the code window is not maximized.



STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.



Steps to Reproduce Behavior
 Create a Standard EXE project in Visual Basic. Form1 is created by default.  Paste the following code in Form1: Private Sub Form_Load Dim x As Integer x = 3 End Sub

 Maximize the code window. From the Edit menu, select Find. Enter 'x' in the Find What text box of the Find dialog box. Click the Find Next command button.</li> Close the code window by clicking on the 'X' button in the upper right hand corner of the code window, not for Visual Basic IDE.</li> Click the Find Next button.</li></ol>

Visual Basic fails with one of the error messages listed in the SYMPTOMS section.

Keywords: kbbug kbnofix kbide KB198605

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.