How to compile and run an OpenEdge application with 32-bit OCX using OpenEdge 12? - Progress Community

Loading

Skip to Main Content

How to compile and run an OpenEdge application with 32-bit OCX using OpenEdge 12?

Starting with OpenEdge 12, OpenEdge Studio(AppBuilder) and Progress Developer Studio for OpenEdge (PDSOE) are no longer available in 32-bit OpenEdge installations. This article explains how to compile and run an OpenEdge application with 32-bit OCX component in OpenEdge 12.

Jun 29, 2021
Knowledge

Title

How to compile and run an OpenEdge application with 32-bit OCX using OpenEdge 12?

URL Name

How-to-compile-and-run-an-OpenEdge-application-with-32-bit-OCX-using-OpenEdge-12

Article Number

000153835

Environment

Product: OpenEdge Version: 12.x Os: Windows

Question/Problem Description

AppBuilder and Progress Developer Studio (PDSOE) were removed from the 32-bit product starting with OpenEdge Release 12.0.

This caused a problem when opening a .w file containing a 32-bit OCX control in either the standalone AppBuilder or PDS for OpenEdge. Doing this in 12.32bit after 12.0 will show the following error message:

Unable to create control.
Specified ActiveX control is not registered or the .ocx file was moved from where it was registered.

This is because 64-bit OpenEdge development environment cannot visualize a 32-bit OCX control.

However, compilation outside of AppBuilder can still be done as long as the .wrx has already been generated.

Since the r-code has no bitness, the compilation can be done with either 32-bit or 64-bit compiler.
Incidental code changes can be done using the ABL Editor (not in Design view).

Sources created in version 11.x including the files with the .WRX extension will need to be carried over from previous releases.

WRX files contain license keys (if ActiveX controls require it) and any custom property settings defined for any ActiveX control in the window.

Attempting to make any changes using the AppBuilder UI (adding/removing widgets or saving) would remove the OCX reference!!

Compilation can be done using the ABL COMPILE statement or the Application Compiler tool found under the 'Tools' menu.

Steps to Reproduce

Clarifying Information

Starting with OpenEdge 12, OpenEdge Studio (AppBuilder) is only available in 64-bit.
Starting with OpenEdge 12, Progress Developer Studio for OpenEdge (PDSOE) is only available in 64-bit.
With OpenEdge 12, the 4GL Development license is available in both 32-bit and 64-bit.
What licenses are required to compile an application with 32-bit OCX with OpenEdge 12?
How to compile and run an OpenEdge application with 32-bit OCX with OpenEdge 12?
How to maintain and compile an application with 32-bit OCX with OpenEdge Studio 12 64-bit?

Error Message

Defect Number

Defect OCTA-30473, OCTA-33655

Enhancement Number

Cause

Defect OCTA-30473 was logged to add AppBuilder binaries back to the installation and to remove the license check that is done by the AppBuilder in order to be able to run it.

Presently this tool checks for the presence of an OpenEdge Studio license to allow it to run the AppBuilder. The fix for this defect would add the AppBuilder product back to 12.x as part of a 4GL Development installation.

Resolution

Upgrade to OpenEdge version 12.2.5 or later.
Upgrade to OpenEdge version 12.4 or later.

The 12.2.5 update and the 12.4 release have re-introduced the AppBuilder to 32-bit OpenEdge. It is now available to run from the installed Program Group icons.

Workaround

In order to use the OpenEdge 12.x 64-bit AppBuilder to edit and save ABL UI, you would need to migrate all 32-bit OCX controls in your application to their 64-bit equivalent (if available).

Notes

References to Other Documentation

Progress Article(s):
Progress OpenEdge Connectivity rules with previous/later versions
What happened to the AppBuilder in 32 Bit 12.0?

Keyword Phrase

Last Modified Date

7/12/2021 11:28 PM

OpenEdge DeploymentOpenEdge ArchitectureOpenEdge DevelopmentOpenEdge General DiscussionsOpenEdge Pro2OpenEdge RDBMS

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

How to compile and run an OpenEdge application with 32-bit OCX using OpenEdge 12? - Progress Community