FIX: Visual Basic 5.0 Crashes When Shutting Down FormsLast reviewed: December 18, 1997Article ID: Q171514 |
The information in this article applies to:
SYMPTOMSClosing a modal form in the Visual Basic 5.0 design environment may cause one of the following errors:
"Access Violation: Unhandled exception in VB5.EXE 0xC0000005: Access Violation" (Windows NT4) -or- "VB has caused an invalid page fault in module VB5.EXE at 0137:00419f1e" (Windows95) CAUSEVisual Basic is trying to get the thread data from a control after it has been unloaded. The error code that signaled that the control got unloaded is not handled properly.
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 INFORMATIONThe Threed32.ocx control shipped with Visual Basic 4.0 is required in order for this behavior to occur. A sample that reproduces this behavior is not available because this behavior tends to occur sporadically, and usually only in large, complex projects. Keywords : vb5all VS97FixlistSP3 VS97FixlistSP2 VB5FixlistSP2 Version : 5.00 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix kbservicepack |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |