BUG: Explicitly Referring to Variables in a Module Causes Error

• Windows CE Toolkit for Visual Basic 5.0, version 1.0

SYMPTOMS

When explicitly referring to variables in a module, such as Module1.Var1, the following error occurs:

   An error was encountered while running this program.

RESOLUTION

Because only one module can be used in Visual Basic 5.0 Windows CE projects, make the variables public. Also ensure that the names of those variables do not conflict with any public variables declared in any form module.

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 Standard Module to the project, named Module1 by default.

3. Add the following code to Module1:

         Option Explicit
         Public VariableInModule
   

4. Add the following code to the code module of Form1:

         Option Explicit
   

         Private Sub Form_Click()
            'This does not work:
            Module1.VariableInModule = "Test"
         End Sub
   
         Private Sub Form_Load()
            'This works:
            VariableInModule = "Test"
            MsgBox "VariableInModule = " & VariableInModule
         End Sub
   
   

5. Press the F5 key to run the project. Note that the form load event executes as expected, and a message box is displayed showing the value of VariableInModule. However, clicking the form generates an error.

Keywords          : vb5all vbce kberrmsg
Version           : WINDOWS:1.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbpending