Kbase 17469: ACTIVEX - Why You Might Be Getting Licensing Problems
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
FACT(s) (Environment):
Windows 32 Intel
Windows NT 32 Intel/Windows 2000
SYMPTOM(s):
Licensing problems with ActiveX
Application was developed with a demo version of the ActiveX
A full version of the ActiveX was purchased, but licensing problem persists.
CAUSE:
When drooping an ActiveX Control (OCX) onto a window, Progress requests two "keys" from the control. Those keys are the "Design Time Key" and the "Run Time Key".
The "Design Time Key" is used to verify that the machine is actually licensed to use the control in design mode.
The "Run Time Key" is written to the *.WRX file and is used when running the application.
The problem shows up when a control is instantiated into the window using an evaluation/demo copy of the control. These evaluation copies typically do not have a valid "Run Time Key". Since Progress does not re-request this key each time the window is saved, there is no way of getting the "valid" key which would exist after the package is purchased and installed.
FIX:
Delete and re-add the control to the application window(s).
Please bear in mind that when the ActiveX control is deleted, all the 4GL triggers associated to that control are deleted as well. Therefore, backup the application code, so that pre-existing triggers can be attached to the new version of the ActiveX control by cut'n'paste in the Section Editor.