Microsoft KB Archive/180818

= BUG: Code Outside of Procedures Executes on Application Startup =

Article ID: 180818

Article Last Modified on 3/11/2005

-

APPLIES TO


 * Microsoft Windows CE Toolkit for Visual Basic 6.0
 * Microsoft eMbedded Visual Basic 3.0

-



This article was previously published under Q180818



SYMPTOMS
Code placed outside of procedures or functions is executed on application startup.



CAUSE
Neither compiler warnings nor errors are 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 that this is a bug in the Microsoft products that are listed at the beginning of this article.



Steps to Reproduce Behavior
 Start a new Windows CE project in either Visual Basic or eMbedded Visual Basic. Form1 is created by default.  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  Press F5 to run the project, and note that the message boxes outside of the event procedures are executed before the Form Load event.

Additional query words: wince 10 wce vbce vbce6 evb

Keywords: kbbug kbtoolkit kbpending KB180818

-

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

© Microsoft Corporation. All rights reserved.