DOCUMENT:Q189914  07-AUG-1998  [vbwin]
TITLE   :BUG: Wrapped CoolBar Control May GPF Client EXE Program
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:5.0
OPER/SYS:WINDOWS
KEYWORDS:

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic for Windows Learning, Professional, and
   Enterprise Editions, version 6.0
 - Microsoft Visual Basic Professional and Enterprise Editions for
   Windows, version 5.0
---------------------------------------------------------------------

SYMPTOMS
========

When you wrap the CoolBar control inside a Visual Basic ActiveX Control,
your Visual Basic client EXE may gave an Illegal Operation error when it
shuts down. This occurs only on Windows 95/98, and when the CoolBar control
has child controls in a band. You will get the following error only in a
compiled EXE and not in the Visual Basic IDE:

   "This program has performed an illegal operation and will be shut down"

RESOLUTION
==========

Clear all the bands from the CoolBar control before the client EXE shuts
down. See Steps to Reproduce Behavior below for an example.

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
================

To reproduce this behavior you must build an OCX that wraps the CoolBar
control and a client EXE that uses that OCX. The EXE must be run on Windows
95/98. The EXE will not give the above error running on NT 4.0.

Steps to Reproduce Behavior
---------------------------

1. Create a new ActiveX Control Project.

2. Using the Projects menu, select Components to bring up the Components
   dialog box. On the Controls Tab, check "Microsoft Windows Common
   Controls-3." Click OK to close the Components window.

3. Place a CoolBar on the UserControl.

4. Change the name of the UserControl to "ctlCoolBar", and the project name
   to "pjxCoolBar." (Do not include the quotation marks.)

5. Place a TextBox, CommandButton, and ComboBox on the CoolBar control.

6. Alternate mouse click on the CoolBar and select Properties from the
   pop-up menu.

7. On the Property Pages dialog box, select the Bands tab.

8. For Index 1, set the Child property to Text1; for Index 2, set the Child
   property to Command1; for Index 3, set the Child property to Combo1.

9. Add the following code to the UserControl:

      Public Sub ClearBands()
         ' clearing all the bands before the control terminates
         ' will keep the client EXE from having the Illegal Operation
         ' error when it shuts down
         CoolBar1.Bands.Clear
      End Sub

10. From the File menu, Save the project, and Make pjxCoolBar.OCX.

11. Create a new Standard EXE Project. Form1 is created by default.

12. Using the Projects menu, select Components to bring up the Components
   dialog box. On the Controls tab, check PjxCoolBar. Click OK to close
   the dialog window.

13. Place the ctlCoolBar control on Form1.

14. From the File menu, Save the project, and Make project1.exe.

15. Run project1.exe and then shutdown project1.exe. You will get the
   Illegal Operation error.

16. To work around the error, add the following code to the Form's
   QueryUnload event.

      ctlCoolBar1.ClearBands

17. Repeat steps 14 and 15. You will not get the error when you shut down
   project1.exe.

Additional query words: kbDSupport kbDSD kbCtrl kbVBp kbVBp600bug
kbVBp500bug
======================================================================
Version           : WINDOWS:5.0
Platform          : WINDOWS
Issue type        : kbbug

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

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.

Copyright Microsoft Corporation 1998.