Microsoft KB Archive/171523
Article ID: 171523
Article Last Modified on 12/10/2003
- 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 Q171523
Trying to reference a non-existent member in an Enum definition will cause Visual Basic 5.0 to crash.
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
Below are two methods for reproducing the problem:
- Start Visual Basic 5.0 and create a new Standard EXE project.
- Add a new Module (Module1) to the project.
Paste the following code into the General Declarations area of Module1:
Public Enum CrashMe Crash1 = Not (Crash0) End Enum
- Invoke the Object Browser by pressing the F2 key, or press the F5 key to run the application. Visual Basic will crash with an Application Error.
- Repeat steps 1, 2, and 3 from Method 1.
- Create a new subroutine named Test in the basic Module.
Type the following in the General Declarations section of Module1:
Public Sub Test() Dim X As
- Press the spacebar. Visual Basic will crash with an Application Error.
NOTE: The program will not crash if you define Crash0 in the declare of the Enum type.
Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171523