BUG: General Protection Fault May Occur When the ComboBox Control Is Set on a Band of CoolBar (269618)

MORE INFORMATION

Steps to Reproduce Behavior

1. Create a Standard EXE project with Visual Basic from Visual Studio 6.0 SP4 in Windows 98. Form1 is created by default.
2. On the Components dialog box, press the CTRL+T keys, select Microsoft Windows Common Controls-3 6.0 (Sp4), and then click OK.
3. Add a CoolBar control to Form1. Use the default settings.
4. Add a ComboBox control inside one of the bands of the CoolBar control.
5. Save the project and press the F5 key to run the application. Click the X in the upper-right corner of the form to close the form, and note that an error message similar to the following appears:
   Filename caused a general protection fault in module USER.EXE at 0004:00000499.
   
   This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor.
   The Filename is the name of your project.
   
   
6. Re-open the project inside the Visual Basic integrated development environment (IDE). Sometimes Windows crashes when Visual Basic is re-opened, and you may need to restart your computer. You may also see a "resource is low" message box indicating that you need to shut down other applications or drivers running in the background.
7. Add the following code to Form1:

   Private Sub Form_QueryUnload(Cancel As Integer, UnloadMode As Integer)
       CoolBar1.Bands.Clear
   End Sub
   						

8. Save the project and press F5 to run the application. Click the X in the upper-right corner of the form to close the form, and note that the project works fine.
   
   NOTE: If you click the End button in the Visual Basic IDE to end the application, note that you continue to see the problem because the Form_QueryUnload event handler does not have a chance to run. Therefore, do not end your application by using the End button in the IDE. To work around this problem, you can replace the SP4 version of the Comct332.ocx file in the system directory with the Visual Studio 6.0 Service Pack 3 version. You still need to implement the workaround mentioned in last step at the same time.