PowerBuilder Support for Long-Running, Mission-Critical Systems
Senior support for PowerBuilder 9 to 2025 R2 — incident triage, small fixes, stabilization and continuity for legacy applications you cannot afford to gamble with. Most engagements start within a week, senior-led from the first call.
PowerBuilder versions and platforms we support
Every release from PowerBuilder 9 to 2025 R2, whatever its status at Appeon or SAP. Find yours below. An upgrade is never a condition of support.
Pick your version on the chart: where it stands today, which .NET runtime it needs and what to do next.
Out of vendor maintenance
9 – 12.6 · 2017 – 2019 R2 · 2021
SAP maintenance ended in June 2018, and Appeon support for these lines by July 2025. We keep them running as they are: crashes, Windows 11 moves, database drivers, lost builds.
Sybase to Appeon migration guidePaid support only
2019 R3 · 2022 · 2022 R2
No more maintenance releases; end of life comes in May 2027 and January 2028. We plan and run the upgrade to 2022 R3 LTS or 2025 R2 before then.
Support dates for every versionSupported
2022 R3 · 2025 · 2025 R2
Appeon still ships maintenance releases. We keep you current, including the .NET 8 end of support on 10 November 2026.
What depends on .NET 8Also in scope: Oracle 11g–21c, SQL Server 2014–2022, PostgreSQL 12–16, InfoMaker, PowerServer, Git, SVN
Typical situations behind a PowerBuilder support call
Reserved capacity gives the business a senior fallback while you decide whether to rehire, retrain or move to a retainer model.
- First callVersion, database, deployment, and what only your developer knows.
- Before they leaveRun book and change log. We work alongside them and write down builds, deployment and the undocumented parts, in plain language, so the knowledge stays with you.
- AfterReserved monthly hours, a named senior consultant, same business-day response.
- Every monthSmall enhancements and patches. DataWindow tweaks, form changes, validation logic, report fields, scoped tightly to keep release risk low.
No one currently in the team has the depth to triage hard PowerBuilder failures fast. We provide that depth on call.
- First callSenior eyes on the current failure within hours, not days.
- Every incidentProduction incident triage and fix. Reproducible test case, root cause, fix and a post-incident note, so the next one is faster.
- Hard casesIntermittent-issue investigation. Race conditions, ODBC quirks, locking, time-zone drift: reproduced and isolated rather than guessed.
- OngoingA guaranteed response window.
Continuity for an application that lost its original consultancy or solo developer. We pick up the system as it is — undocumented .pbl files included.
- FirstWe take the system as it is: source, builds, environments, undocumented .pbl files.
- NextDataWindow and PBL repair. Broken DataWindow objects, corrupted .pbl files, lost references and window inheritance, restored without losing custom code.
- ThenDatabase adjustment under the application. Stored procedures, packages, triggers and views: small targeted changes that keep the application stable while the schema evolves.
- OngoingA run book of what we found, a named senior consultant and, on longer retainers, a named secondary.
Broken build, lost installer, missing signing certificate, runtime drift. We rebuild the deployment path so releases stop being events.
- FirstBuild, deployment and installer recovery. The build chain and version control repaired, the installer regenerated, the signing certificate rolled over, runtime distribution fixed.
- Every releasePatch and hotfix coordination. PowerBuilder runtime and Appeon patch tracking, regression checks, a planned rollout with rollback gates.
- ResultReleases stop being events.
Reserved capacity, on-demand, or fixed-scope
| Engagement | Best for | Commitment | Response | Price |
|---|---|---|---|---|
| Ad hoc consulting | Occasional analysis, troubleshooting, a second opinion | None: hours per engagement | Same week | Hourly, on request |
| Monthly Support Retainer | Incidents, small changes and the run book on a live system | Reserved monthly hours, quarterly review | Same business day | Tailored to scope and responsibility |
| Fixed-scope rescue | One defined problem: build recovery, certificate rollover, an incident's root cause | One scope, one timeline | Scoped milestones, hard deadline | Fixed fee, scope-dependent |
From first call to steady state
Intake1–3 days
Short triage call: version, database, deployment shape, current pain. Scope and response cadence agreed.
Reserved capacityMonthly
Fixed monthly hours, a guaranteed response window and a named senior consultant, not a rotating queue.
Run bookWith every fix
Every non-trivial fix lands in a plain-language change log: what changed, why, how to roll back.
Quarterly reviewEvery 3 months
What we did, what's stable, what's drifting, what to plan for the next 90 days.
What teams ask before they call
Not on the list? Ask us directly — we usually reply within one business day.
Which PowerBuilder versions do you support?
PowerBuilder 9 to 12.6 from the Sybase and SAP era, and Appeon releases from 2017 to 2025 R2 — including InfoMaker reports and PowerServer deployments. On Appeon's side, the lines still receiving maintenance releases are 2022 R3 (LTS), 2025 and 2025 R2; SAP ended mainstream maintenance for 12.6 and earlier on 30 June 2018.
How fast can you start?
Most engagements begin within a week of the first call. If the situation is genuinely urgent — production down, key developer leaving in days — we can usually start the same week and adjust paperwork in parallel.
We're on PowerBuilder 9 / 10 / 11. Is that a problem?
No. The bulk of the systems we support are on legacy Sybase-era PowerBuilder (9, 10.5, 11.5, 12.6). We won't push you to upgrade as a condition of support — modernization is a separate decision, made on your terms.
Do you support PowerBuilder applications on Windows 11 and Windows Server 2025?
Yes. When an application breaks after a Windows move, the cause is usually a runtime that doesn't match the build, a database driver mismatch or high-DPI rendering in older code — all fixable without a rewrite.
Our security team is removing .NET 8. Does that affect our PowerBuilder application?
It can. On PowerBuilder 2025, and on 2022 R3 builds MR 3391 to 3452, the ADO.NET database interface and .NET assembly calls need .NET Desktop Runtime 8.0 on each client. 2022 R3 MR 3487 and 2025 R2 support .NET 10 instead; .NET 8 goes out of support on 10 November 2026.
Can you work alongside our existing developer?
Yes — and often that's the cleanest setup. We bring depth on the rare PowerBuilder problems while your team owns day-to-day delivery. Communication channel and ticket flow are agreed up front so we're not in each other's way.
What if our consultant on your side becomes unavailable?
Each engagement is owned by a senior consultant from the first call to the last. For longer-running retainers we maintain a documented run book and a named secondary so the engagement survives illness, holidays and other realities.
How is PowerBuilder support priced?
In one of three shapes: hourly for occasional work, a monthly retainer with reserved hours and a guaranteed response window, or a fixed fee for one defined problem. We suggest the fit after a short intake call and agree the scope before any work starts.
Do you sign NDAs and have a standard MSA?
Yes. We sign your NDA before any code review or system description is shared. We have a Master Services Agreement template that works for most enterprises; we're also happy to work under yours. References available on request.
Need senior PowerBuilder support?
Send a short description of your system — versions, databases, integrations and the situation you're in. We'll reply within one business day with a practical next step, sized to your scope and risk.