Mike Fechner (Consultingwerk) asked a question.

Time to retire your Active X Controls! You've got 5 years!

Progress has documented this in the knowledge base: https://community.progress.com/s/article/end-of-32-bit-windows-support-in-openedge

 

The key point: OpenEdge 13.2 drops support for 32-bit runtimes. OpenEdge 12.8 — the last LTS release with 32-bit support — retires in five years, so that retirement date is effectively your final deadline for getting rid of ActiveX controls. The 64-bit client can host ActiveX controls in principle, but only if a 64-bit build of the control exists — and in practice many vendors never shipped one. Where the vendor is gone or the control is unmaintained, there's no 64-bit OCX to fall back on, so the dependency has to be removed rather than ported.

 

A few migration paths, roughly in order of effort:

 

  • Embed the ABL GUI window in a .NET form and overlay .NET controls. The .NET controls are fully supported on 64-bit, so individual ActiveX controls can be replaced in place without rewriting the whole window. The lowest-risk path for incremental migration.

 

  • Transform the ABL GUI into a GUI for .NET. More involved, but it gets you onto a control stack that is natively 64-bit.

 

  • Move the application to a browser-based UI. The largest change, and the sensible one where the long-term target is a web frontend anyway.

 

One thing worth noting on the effort side: the repetitive parts of this work — mapping controls, rewriting event handlers, restructuring window logic — are now much more tractable with AI-assisted tooling than they were even a couple of years ago. That doesn't remove the architectural decisions, but it does lower the mechanical cost of a migration significantly that previously looked like pure overhead.

 

Five years sounds like plenty of runway, but ActiveX removal tends to surface coupling you didn't know was there. It's worth starting the inventory early — which controls you actually depend on, and which of those have no 64-bit future.


  • Tony Prettyman (Progress Software)

    We have not changed our mind. 13.2 will not contain a Win32 download. There is a more formal communication in the works with approved language. This PANS notice came out prematurely. Look for an update in the near future and when it happens we will update the PANS notice language as well and share it again.

     

    Tony Prettyman

    Sr Director Product Management - OpenEdge

    Selected as Best
  • Frank Meulblok (Customer)

    5 years...

    Unless Microsoft decides to completly shut down ActiveX support before that. And while I don't think that will happen *that* fast, they are making it more difficult to support the controls due to changes in default security policies etc.

    So I do expect it to become more difficult to keep things running as-is.

     

     In other words, there's more good reasons to phase out your ActiveX components before you hit harder deadlines.

    • Mike Fechner (Consultingwerk)

      This just gives us more reasons to act fast!

  • Neil Treeby (D&H Distributing)

    Moving fully to 64-bit (and ditching most if not all of our ActiveX controls - we may still have a PSTimer or two hiding somewhere) when we went from 10.2B to 11.7.x between 2018-2020* was a smart move, then?

     

    I also got to play with some interesting hardware during the testing phase of moving from 32-bit OCX to 64-bit DLL interfaces - I had a rather heavy warehouse scale on my desk for the better part of a year, and testing the package measuring device and vacuum sealing machine meant a visit to the DC. Quite exciting for a desk jockey!

     

    * Technically 2021, we had to keep some of our DBs and codebase on 10.2B for about a year because of an ancient legacy Java app that couldn't talk to 11.7.x AppServers. Swapped that app out for browser frontend and PASOE REST backend.

  • Lieven De Foor (TVH Parts Holding)

    Another possibility is to wrap .NET controls in a 64-bit OCX.

    This should now work in 12.8 according to the release notes, see https://community.progress.com/s/question/0D74Q0000098eVpSAI/detail (scroll all the way down).

    I requested this a while ago, but didn't try it out after changing jobs...

    It allows to keep a classic GUI and only replace the 32-bit ocx with a 64-bit equivalent, delegating implementation to a .NET control (e.g. a .NET TreeView)...

  • Lieven De Foor (TVH Parts Holding)

    The link at the top no longer works...

    Has Progress changed its mind?

  • Tony Prettyman (Progress Software)

    We have not changed our mind. 13.2 will not contain a Win32 download. There is a more formal communication in the works with approved language. This PANS notice came out prematurely. Look for an update in the near future and when it happens we will update the PANS notice language as well and share it again.

     

    Tony Prettyman

    Sr Director Product Management - OpenEdge

    Selected as Best