BUG: Stop Statement in ActiveX Server Causes VB to Fail

MORE INFORMATION

Steps to Reproduce Behavior

1. Create a new ActiveX DLL project in Microsoft Visual Basic. Class1 is created by default.
2. On the Project menu, select Project1 Properties.
3. In the Project name box, enter "MyDLL" (without the quotes) and click OK.
4. Enter the following code to Class1 of MyDLL:

         Public Sub Test()
            Stop
         End Sub
   
   						

5. On the File menu, click Make MyDLL.dll.
6. Create a new Standard EXE project in Microsoft Visual Basic. Form1 is created by default.
   
   NOTE: If desired, you can save the MyDLL project.
7. On the Project menu, click References.
8. In the Available References list, click to select a reference to MyDLL, and then click OK.
9. Add a CommandButton to Form1, and add the following code to the code window of Form1:

         Public Sub Command1_Click()
            Dim x as New Class1
            x.Test
         End Sub
   
   						

10. Press the F5 key to run the project, and click on the CommandButton.

At this point, the following error occurs:

Once you click OK to continue past this dialog, a second error dialog is displayed:

Click Debug on this dialog to debug the Standard EXE. If you press the F5 key again to run the code, Visual Basic will fail. If you choose End at this dialog, Visual Basic will end the debug session correctly.

For an ActiveX EXE (server) project under the same condition, after step 8 Visual Basic generates the following run-time error instead of the crash:

If Debug is chosen, connections to the server are lost and the application stop responding until it is closed.