PowerBuilder
Rapid development tool for enterprise client/server applications, known for its DataWindow component. Created by Powersoft in 1991 and now developed by Appeon.
Pronunciation
What is it
PowerBuilder is a development environment for building database-driven business applications: data entry forms, queries, reports. Its language is called PowerScript and its best-known piece is the DataWindow, a component for visually designing how data is queried, edited, and displayed.
If your company runs a desktop system that “talks directly to the database” and was built in the 90s or 2000s, there’s a good chance it’s PowerBuilder, VB6, or Delphi.
A Bit of History
| Year | Milestone |
|---|---|
| 1991 | Powersoft releases PowerBuilder 1.0, with the DataWindow and PowerScript |
| 1995 | Sybase completes its acquisition of Powersoft |
| 2010 | SAP acquires Sybase and, with it, PowerBuilder |
| 2016 | Under an agreement with SAP, Appeon takes over PowerBuilder development, sales, and support |
As of this entry, the latest version is PowerBuilder 2025 R2. Appeon also offers PowerServer, which deploys existing client/server applications as installable cloud apps with a REST API architecture.
Typical Client/Server Architecture
[User's PC] [Server]
PowerBuilder app ──────── SQL ───────→ Database
(UI + DataWindow + (Oracle, SQL Server,
business rules) SQL Anywhere, etc.)The whole application lives on the user’s machine and connects directly to the database. It works well on an internal network, but makes remote access, mobile apps, scalability, and security harder.
Why It Matters for Your Company
- Scarce talent: few new developers learn PowerBuilder
- Trapped logic: business rules spread across DataWindows, scripts, and stored procedures
- Costly distribution: installing and updating clients on every machine
- Limited integration: connecting to cloud services, mobile apps, or AI takes extra work
In companies and public agencies across the region, it’s not unusual to find PowerBuilder systems that are still critical to operations.
Modernization Options
| Option | When it makes sense |
|---|---|
| Upgrade to the current PowerBuilder version | You want to keep the stack and the team knows it |
| Move to the web with vendor tooling | You need remote access quickly without rewriting |
| Rewrite in slices to .NET + Angular | You want a modern web architecture, open APIs, and a stack with a larger talent pool |
Common Mistakes
❌ Underestimating DataWindows → Each DataWindow combines query, validation, formatting, and presentation; replacing one is more than “building a screen”
❌ Migrating the UI and leaving database logic unreviewed → Stored procedures are also part of the technical debt
❌ Not measuring actual usage → Many systems have modules and reports nobody uses; migrating them is pure cost
Practical Example (illustrative)
A healthcare company runs a PowerBuilder system for admissions and billing. An incremental modernization plan:
- Map DataWindows and group them by business process (admission, authorization, billing)
- Build .NET APIs for the admission process, reusing the existing database
- New Angular web screen for admissions, while billing stays in PowerBuilder
- Repeat per process following the Strangler Fig pattern until the desktop client is retired
Do your operations depend on PowerBuilder? At Nextsoft we support these projects together with specialized strategic partners: the partner carries out the migration and Nextsoft delivers new modules, integrations, frontend and QA. Explore the legacy system modernization service or book a conversation.
Related Terms
- VB6 - Contemporary desktop tool, no longer supported for development
- Delphi - Another enterprise RAD platform from the same era
- Technical Debt - The accumulated cost of postponing modernization
- Strangler Fig - Pattern for replacing the system piece by piece
- API - The layer that replaces direct database connections
Additional Resources:
- Appeon - PowerBuilder - Official product site