BUG: Code Outside of Procedures Executes on Application Startup

• Windows CE Toolkit for Visual Basic 5.0, version 1.0

SYMPTOMS

Code placed outside of procedures or functions will be executed on application startup.

CAUSE

Compiler warnings or errors are not generated.

RESOLUTION

Do not place code other than declarations outside of subs, functions, or event procedures.

Although this could be used for the same purpose as a SubMain or the Form Load event, it is strongly recommended that this behavior be avoided to provide future compatibility.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

1. Start a new Windows CE Project in Visual Basic 5.0. Form1 is created by default.

2. Place the following code in the code module for Form1:

         Option Explicit
   

         Dim myMessage
         myMessage = "Hello from the Declarations section of Form1."
         MsgBox myMessage
   

         Private Sub Form_Click()
             MsgBox "Hello from the Form Click event."
         End Sub
   
         MsgBox "Hello from somewhere else."
   
         Private Sub Form_Load()
             MsgBox "Hello from the Form Load event."
         End Sub
   
   

3. Press the F% key to run the project, and note that the message boxes outside of the event procedures are executed before the Form Load event.

REFERENCES

Online Book for Microsoft Windows CE Toolkit for Visual Basic 5.0