DOCUMENT:Q190068  07-AUG-1998  [vbwin]
TITLE   :BUG: Control Interface Wizard May Not Expose BackColor Property
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:6.0
OPER/SYS:WINDOWS
KEYWORDS:kbVBp600bug kbWizard kbNTOS kbWinOS

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

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

SYMPTOMS
========

After you have used the ActiveX Control Interface Wizard to expose both the
Appearance and BackColor properties of a control and you use the control in
a project, any changes that you make to the BackColor property in the
control's Properties window do not appear when you run the project.

RESOLUTION
==========

You can manipulate the desired properties in code, or you can choose not to
expose the Appearance property.

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


Create a UserControl Using the ActiveX Control Interface Wizard:

1. Start Visual Basic 6.0, and open a new ActiveX Control project. Place a
   command button on the UserControl.

2. From the Add-Ins menu, select Add-In Manager and double-click "VB 6
   ActiveX Ctl Interface Wizard" in the Available Add-Ins column. Click OK
   to dismiss the dialog.

3. From the Add-Ins menu, select ActiveX Control Interface Wizard.

   NOTE: If the Introduction screen for the ActiveX Control Interface
   Wizard appears, click Next.

4. In the Select Interface Member screen, choose the Appearance property
   from the Available Names list on the left, click the ">" button to
   add it to the Selected Names list on the right. Click Next.

5. When the Create Custom Interface Members screen appears, click Next.

6. In the Set Mapping window, under the Public Name list, select the
   Appearance and BackColor properties for the UserControl member in the
   Control and Member lists. Click Next.

7. In the Set Attributes window, click Finish. Click Close to quit the
   ActiveX Control Interface Wizard Summary dialog box.

8. From the File menu, select Make Project1.ocx to compile the control.


Test the UserControl in Another Project:

1. Create a new Standard EXE project.

2. Select Components from the Project menu. Add the UserControl to the
   toolbox by selecting it from the list and clicking Apply.

3. Place the UserControl from the toolbox onto Form1 in your Standard EXE
   project.

4. In the Properties window, change the BackColor Property of the ActiveX
   Control to Red.

5. Press the F5 key to run the project.

RESULT: The UserControl appears with the design-time BackColor (based on
the Appearance Property setting) instead of the BackColor (Red) that you
chose in the Properties Window for that control.

Additional query words:
======================================================================
Keywords          : kbVBp600bug kbWizard kbNTOS kbWinOS
Version           : WINDOWS:6.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.

Copyright Microsoft Corporation 1998.