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

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.
 

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?
 

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.
 

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.

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).
 

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?