BUG: Private UserControls Do Not Support Data BindingLast reviewed: August 4, 1997Article ID: Q172056 |
The information in this article applies to:
SYMPTOMSA 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.
CAUSE
RESOLUTIONThe 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.
STATUSMicrosoft 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
REFERENCESFor more information about licensing processes, see the Microsoft Visual Basic Books Online: Component Tools Guide Creating ActiveX Components Building ActiveX Controls Distributing Controls Keywords : vb5all Version : 5.0 Platform : WINDOWS Issue type : kbbug |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |