BUG: VBCE Control Manager Only Recognizes First Control in DLL (247723)
The information in this article applies to:
- Microsoft Windows CE Toolkit for Visual Basic 6.0
- Microsoft Windows CE Toolkit for Visual C++ 6.0, when used with:
- Microsoft Windows CE 2.0 for the Handheld PC
- Microsoft Windows CE 2.11 for the Handheld PC
- Microsoft Windows CE for the Palm-size PC, Versions 2.11
This article was previously published under Q247723 SYMPTOMS
Because the Windows CE Toolkit for Visual Basic (VBCE) does not support control creation, it is common to create ActiveX controls with the Windows CE Toolkit for Visual C++ (VCCE) and host them on VBCE forms.
When a VCCE DLL contains multiple ActiveX controls or property pages and is registered using the Control Manager so that you can host the controls on VBCE forms, the controls are added to the Visual Basic toolbox, but only the first control can be added to the form.
The problem only occurs on the Handheld PC Pro and Palm-size PC platforms.
CAUSE
The problem is caused by a bug in the Control Manager, which only recognizes the GUID of the first control in the VCCE DLL.
RESOLUTION
The workaround is to have one ActiveX control per DLL. If the control needs to have property pages, make sure that the GUID for the control itself is listed first in the IDL file instead of the property pages.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. REFERENCES
For information on how to create ActiveX controls for Microsoft Windows CE, please check the white paper at:
Modification Type: | Minor | Last Reviewed: | 8/19/2005 |
---|
Keywords: | kbBug kbpending kbToolkit KB247723 |
---|
|