// blog

PowerBuilder to the Web: What Happens to DataWindows and PowerScript

When a PowerBuilder application moves to the web, each DataWindow becomes a web screen, grid or report with the same columns, filters and totals, and its SQL is kept or rewritten with results compared against the old one. Rules in PowerScript events and functions are written down and built once on the server. The Oracle, SQL Server or SQL Anywhere database can stay, stored procedures included, or move to PostgreSQL.

Last updated 1 min read

A table: DataWindows become web screens, PowerScript becomes written rules, the database stays

PowerBuilder was built for one thing, data-heavy business screens, and it did it well. Many of those client-server apps are still running. The hard part now is finding people to change them.

DataWindows

The DataWindow is the heart of a PowerBuilder app: a screen, a grid or a report, with its SQL inside. Each one becomes a web screen, grid or report with the same columns, filters and totals. Its SQL is kept or rewritten, and the results are compared with the old DataWindow on your own data.

PowerScript

Rules live in PowerScript events and functions, and often in the database too. Each rule is written down as a plain sentence, checked by the people who use the app, and built once on the server.

The database

It can stay. The web version can work against your Oracle, SQL Server or SQL Anywhere database, stored procedures and triggers included, or the data moves to PostgreSQL. You decide in the proposal.

Nothing to install

The client install on every PC goes away. The app opens in any browser, from the office or from home.

See how a PowerBuilder app moves to the web. The first call is free.