DOCUMENT:Q188552  29-JUN-1998  [vbwin]
TITLE   :BUG: UserControl's ContainedControls Do Not Inherit ScaleMode
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 Learning, Professional, and Enterprise Editions
   for Windows, version 5.0
---------------------------------------------------------------------

SYMPTOMS
========

A control in the ContainedControls collection of a UserControl reports its
dimensions and placement in Twips regardless of the ScaleMode setting of
the UserControl or the Parent. Because ScaleMode is inherited elsewhere in
Visual Basic, this behavior is inconsistent.

RESOLUTION
==========

Programmatically, you can use the ScaleX and ScaleY methods to convert the
property values from one ScaleMode to another. Note that this does not
change the actual ScaleMode of the properties. ScaleX and ScaleY are merely
conversion functions. There are no workarounds for how the properties are
reported in the Property Windows.

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. Start a new Standard Exe project in Visual Basic. Form1 is created by
   default.

2. Set the ScaleMode property of Form1 to 6 - Millimeters.

3. Add a UserControl to the project.

4. Set the ScaleMode property of the UserControl to 6 - Millimeters.

5. Set the ControlContainer property of the UserControl to True.

6. Close the UserControl window.

7. Place the UserControl on Form1.

8. Drag a CommandButton onto the UserControl.

9. Drag a CommandButton onto Form1.

10. View the Properties for the UserControl (such as Width) and note that
   all coordinates are reported in millimeters.

11. View the Properties for the two CommandButtons. Compare the Width of
   the CommandButton placed inside the UserControl with the CommandButton
   placed onto the Form. Notice the Width of the CommandButton placed
   inside the UserControl is in Twips whereas the Width of the
   CommandButton placed on the Form is in millimeters.

Additional query words: kbDSupport kbDSD kbVBp kbCtrl 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.