Progress OpenEdge non-UI licensing

[chrisjones]

We would like to move a customer from Community to Professional VPE. We cannot licence the VPE control. Our dev environment is Progress OpenEdge. The licencing works fine in the GUI interface as Progress tools will create a .wrx file which embeds the licence details. We wish to run VPE on a server machine with no GUI interface. This works great with the community edition. We can just use
CREATE "VpeControl.VpeControl.71" phHandle, as this does not require licensing so does not require a .wrx file. We cannot licence the Professional addition as Progress do not support the .wrx files in a non GUI environment. I have raised this with Progress tech support but they have said that this cannot be done. Is there any way that I can licence the VPE professional runtime product without a Progress .wrx file?

[IDEAL Software Support]

We can create C++ source code to license the VPE ActiveX. Contact us by e-mail to discuss the cost for development.

[ZensoftBelgiumHZ]

We would like to move a customer from Community to Professional VPE. We cannot licence the VPE control. Our dev environment is Progress OpenEdge. The licencing works fine in the GUI interface as Progress tools will create a .wrx file which embeds the licence details. We wish to run VPE on a server machine with no GUI interface. This works great with the community edition. We can just use
CREATE "VpeControl.VpeControl.71" phHandle, as this does not require licensing so does not require a .wrx file. We cannot licence the Professional addition as Progress do not support the .wrx files in a non GUI environment. I have raised this with Progress tech support but they have said that this cannot be done. Is there any way that I can licence the VPE professional runtime product without a Progress .wrx file?

Licensing in Openedge for .NET Controls is explainded in KB:
https://knowledgebase.progress.com/arti ... ontrol-NET