DOCUMENT:Q192647  14-SEP-1998  [vbwin]
TITLE   :INFO: Visual Basic Reserves OCX Resource IDs Starting at 30000
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:5.0,6.0
OPER/SYS:WINDOWS
KEYWORDS:

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

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

SUMMARY
=======

In accordance with the specifications for building and exposing ActiveX
controls, Visual Basic uses a resource file to store the toolbox bitmaps
for each UserControl in a compiled OCX. Design-time clients can then load
and display these bitmap images in a "control toolbox" without having to
load or create running instances of these controls.

By default, Visual Basic stores these images with a base resource
identifier starting at 30000. Consequently, when adding your own resource
file to a Visual Basic ActiveX control project, you should avoid using
resource IDs that might conflict with these values.

MORE INFORMATION
================

The toolbox image resource ID for a UserControl is registered on the system
in the ToolboxBitmap32 registry key under the CLSID for the control.

REFERENCES
==========

"Working with Resource Files" in the Visual Basic 6.0 Online Help

"More About Programming: Working with Resource Files" in the Visual Basic
5.0 Books Online

Additional query words: kbDSupport kbDSD kbVBp kbVBp500 kbVBp600
kbCtrlCreate kbActiveX
======================================================================
Version           : WINDOWS:5.0,6.0
Platform          : WINDOWS
Issue type        : kbinfo

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

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.