Kbase P28362: Cannot open .w file containing Microsoft common control OCX in AppBuilder
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/01/2009 |
|
Status: Verified
SYMPTOM(s):
Cannot open .w file containing Microsoft common control OCX in AppBuilder
Cannot add Microsoft Common Control version 5 controls to existing windows
Cannot develop with controls contained in the Microsoft COMCTL32.OCX library
The following error occurs:
CtrlFrame.<name of control>
Unable to create control.
The license file for the specified ActiveX control was not found.
FACT(s) (Environment):
Using the version 5 set of the Microsoft common controls (TabStrip, ProgressBar etc.)
Progress 9.x
OpenEdge 10.x
Windows
CAUSE:
In later versions of Windows, the version 5 OCXes are supplied only for backwards compatibility, and no development licenses are supplied for them.
FIX:
The preferred resolution to this issue is to install a Microsoft Development product. It has been confirmed that up to the Visual Studio 6 series, the required development license for the version 5 controls are included.
Alternatively, it is possible to manually migrate the OCX to Version 6, for which a development license should be supplied with the OS.
To do this:
- Use RegEdit to track down the CLSID of the version 5 control and the version 6 equivalent. (These are stored under HKEY_CLASSES_ROOT\CLSID)
- Open the .w file in an ascii editor.
- Find the definition for the section "Create OCX containers" and in that
section, find the CLSID of the version 5 control.
- Replace this with the CLSID of the version 6 control.
- Rename/delete any .wrx files belonging to the .w.
- Open the .w file in AppBuilder and reapply the required settings to the control.