Q180760

• Microsoft Windows CE Toolkit for Visual Basic 5.0, version 1.0

SYMPTOMS

Form Activate events may not fire correctly after a form is closed and then reopened.

RESOLUTION

Remove ControlMenus, MinButtons, and MaxButtons from all forms (set their properties to False), and use menu or command button code to close forms.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article.

This problem was corrected in Windows CE Toolkit for Visual Basic 6.0.

MORE INFORMATION

The problem is difficult to reproduce. It only occurs when a form is closed using the Control Menu or Window Close buttons (upper-right corner), and then reopened while the application continues to run.

NOTE: This problem does not occur when the Hide and Show method are used tonavigate among forms.

Steps to Reproduce Behavior

1. Open a new Windows CE project in Visual Basic 5.0. Form1 is created by default.



2. Add another form (Form2) to the project.



3. Add a CommandButton (Command1) to Form1 and paste the following code into the General Declarations section of Form1:
   

   
         Private Sub Command1_Click()
            Form2.Show
         End Sub 




4. Add a CommandButton (Command1) to Form2 and paste the following code into the General Declarations section of Form2:
   

   
         Private Sub Command1_Click()
            Form1.Show
         End Sub
   
         Private Sub Form_Activate()
            MsgBox "Form2 is activated"
         End Sub 




5. Press the F5 key to run the project in emulation.



6. Click Command1 on Form1. Form2 is brought to the front and the message box indicates that the Form2 Activate event was fired. Click OK to clear the message box.



7. Click Command1 on Form2. Form1 is brought to the front. Click the "X" button to close Form1. Form2 Activate is fired again. Clear the message box.



8. Click Command1 on Form2 to bring up Form1. Click Command1 on Form1. Form2 shows, but the message box in the Form2 Activate event does not fire.

Additional query words: vbce5 vbce6 vbce

Keywords : kbToolkit kbVBp kbVBp500bug kbVBp600fix kbOSWinCEsearch kbOSWinCE100 kbGrpDSVB
Issue type : kbbug
Technology : kbVBSearch kbAudDeveloper kbWinCETKVBSearch kbWinCESearch kbWinCETK100VB500