BUG: Private UserControls Do Not Support Data Binding (172056)
The information in this article applies to:
- Microsoft Visual Basic Control Creation Edition for Windows 5.0
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q172056 SYMPTOMS
A UserControl created within a Standard EXE as a private object will not
correctly bind its defined bound properties after the application is
compiled to an EXE. While the application is debugged in the Visual Basic
5.0 IDE, the control and its binding function correctly.
CAUSERESOLUTION
The only workaround is to compile a separate binary for the OCX to be a
public control. In this fashion, the bindable public properties function
correctly.
To hide the use of this control adequately from other applications (one of
the main benefits of a private UserControl) the author should add run-time
licensing support to minimize the use of the control outside the intended
application.
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.
REFERENCES
For more information about licensing processes, see the Microsoft Visual
Basic Books Online:
Component Tools Guide
Creating ActiveX Components
Building ActiveX Controls
Distributing Controls
Modification Type: | Major | Last Reviewed: | 11/18/2003 |
---|
Keywords: | kbbug KB172056 |
---|
|