Mike Fechner (Consultingwerk) asked a question.
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.

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