What we see with PowerBuilder
PowerBuilder applications with DataWindow-based screens and database back ends.
Typical situations:
- A PowerBuilder client that runs on a few aging computers.
- Source libraries that no one has opened in years.
- A vendor license question nobody can answer.
What we do
- Secure the libraries and the environment needed to open them.
- Document screens, data access and deployment.
- Discuss a plan in writing: sustain it or move it, in stages.
What this includes
PowerBuilder applications, DataWindow objects and the databases behind them.
By arrangement
PowerBuilder is supported by arrangement. We start with a Takeover Assessment to see what you have and what is feasible. For this stack we may bring in a specialist for part of the work, and we say so in the written scope and the quote before anything begins. We will tell you plainly if we are not the right fit.
Every engagement starts read-only. We write write-access terms into a signed agreement first, and a person reviews every change before it reaches a live system. Our work is AI-assisted and human-reviewed, and we tell you how at the start.
Tell us about your PowerBuilder software and we will reply by email with what we would look at first.