BUG: Sub Main Does Not Transfer Control to Form

Last reviewed: February 5, 1998
Article ID: Q180528
The information in this article applies to:
  • Windows CE Toolkit for Visual Basic 5.0, version 1.0

SYMPTOMS

When a Windows CE project has a module with Sub Main set as the Startup Object, control of the application does not transfer to a form when the Sub Main is finished, causing the application to end prematurely.

RESOLUTION

Avoid using Sub Main as the Startup object. Use a form as the Startup object.

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. Create a new Windows CE Project in Visual Basic 5.0. Form1 is created by default.

  2. Add a new module to the project by selecting Add Module from the Project menu.

  3. Add the following code to Module1:

          Sub Main()
              Form1.Show
          End Sub
    
    

  4. Select Project1 Properties from the Project menu.

  5. Set the Startup Object to Sub Main.

  6. Press the F5 key to run the project and note that the application will end when sub main execution is completed instead of passing control of the application to Form1.

(c) Microsoft Corporation 1998, All Rights Reserved. Contributions by Mike Dixon, Microsoft Corporation
Keywords          : vb5all vbce
Version           : WINDOWS:1.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbpending


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 5, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.