Which PowerBuilder version should you be on?

What is still supported, what is frozen, and how to tell a straightforward upgrade from a genuine project.

Request a free application review +44 (0)1293 562730
Horsham, West Sussex
a UK team you can meet
1 of only 2
Appeon partners in the UK
PB v4 → PB2025
every release in between
Since 1986
40 years trading

The short answer

You should be on a current Appeon long-term support release. Everything else is a question of how far away from that you are and how much it is worth spending to close the gap.

That sounds like the answer a consultancy would give, so here is the reasoning. Appeon PowerBuilder is the only version of PowerBuilder that still receives bug fixes and new features. Every release before that is frozen. Frozen is not the same as broken — plenty of organisations run frozen software perfectly happily for years — but it does mean that when something around your application changes, and it will, the fix has to come from somewhere other than the vendor.

The things that change around a PowerBuilder application are predictable: Windows versions, database versions and drivers, Microsoft Office integration, security policy, and the move from 32-bit to 64-bit. Each of those is a reason a stable application suddenly stops being stable.

Free analysis first

Before you budget anything, we will review your application and tell you whether a version move is straightforward, complex, or genuinely not worth doing yet. It costs you nothing and it is the honest way to size the work.

The versions in play

Supported by Appeon

Appeon PowerBuilder is the only version of PowerBuilder that still receives bug fixes and new features. The releases marked LTS are the long-term support versions, and they are what we build new systems on.

PB2017 PB2017r2 PB2017r3 (LTS) PB2019r3 (LTS) PB2022R3 (LTS) PB2025

Supported by us

Appeon issues nothing for these any more. We still support them: troubleshooting, workarounds and keeping the thing running. What we cannot do is issue a patch to PowerBuilder itself.

6.0 6.5 7.0 7.5 8.0 8.5 9.0 9.5 10.0 10.5 11.0 11.5 12.0 12.5 12.6 EAServer 5 & 6

On something not listed here? Ring us. We have seen most of it.

Three questions that decide it

What is changing around you?

A Windows Server refresh, an Oracle or SQL Server upgrade, a move to 64-bit, or a security review are the usual triggers. If none of those is coming, the pressure is lower than you think.

Who can still change the code?

A frozen version is only comfortable while somebody understands the application. If that person is retiring, the version question and the people question are really the same question.

What do you want it to do next?

Web or cloud access, API integration and modern authentication all need a current release underneath them. If any of that is on the roadmap, the version move is the first step whether you like it or not.

What actually breaks between versions

In our experience the migration itself is rarely the hard part. The hard parts are the things bolted to it: native database drivers that no longer exist, ODBC connections that behave differently, third-party controls whose vendors have vanished, Java components that ran under an old EAServer and will not run under a newer one, and Office integration written against a version of Office that shipped two decades ago.

We know that because we have unpicked all of it. COWI's Caretaker application was stuck on PowerBuilder 7 precisely because of MS SQL Server retrieval errors, an ODBC-only connection where a native driver was wanted, and translation software that had stopped working. Teachers Assurance needed legacy Java rewritten in PowerBuilder because it would not run under EAServer 5.5 or 6.3. That is the shape of the work.

Legacy PowerBuilder releases from the Powersoft, Sybase and SAP eras

Questions people ask us about this

Is PowerBuilder still supported in 2026?

Yes. Appeon actively develops PowerBuilder and issues regular releases, including long-term support versions. Appeon PowerBuilder is the only version that receives bug fixes and new features; releases from the Sybase and SAP era do not.

What is the latest version of PowerBuilder?

PB2025 is the current release. PB2022R3, PB2019r3 and PB2017r3 are long-term support releases, which is what most organisations standardise on.

Can you still support PowerBuilder 9 or PowerBuilder 11?

Yes. We support every release from PowerBuilder 6.0 through 12.6, plus EAServer 5 and 6. We cannot issue patches to PowerBuilder itself for those versions, but we can troubleshoot, find workarounds and keep the application running.

How much work is it to move from an old version to a current one?

It depends almost entirely on where you are starting and what your application touches. Moving from a late release can be close to a straight recompile; moving from PowerBuilder 6 with old database drivers and third-party controls is a project. Our free analysis tells you which of those you are looking at before you commit any budget.

Not sure which of these applies to you?

Tell us the PowerBuilder version you are on, the database behind it and what is worrying you. We will give you an honest read on your options, including whether the answer is to do nothing for now. The initial review of your application is free, and we are close enough to come and see you.

Telephone: +44 (0)1293 562730

Email: sales@powersoft-services.co.uk

Appeon approved consulting partner