Auto-detect PowerBuilder project format (Exported Solution vs Binary Workspace), read source files appropriately, and extract complete migration artifacts.
Point your AI agent at a PowerBuilder project folder. It will auto-detect the format and read source files accordingly.
Example prompts you can give your AI agent:
Analyze this PowerBuilder project folder for FlexBase migrationRead this PowerBuilder application and extract all DataWindows, windows, and user objectsDetect the PowerBuilder format and extract migration data from this folderPowerBuilder projects exist in two distinct formats:
Exported Solution
.pbl entries are folders with text source files (.srd, .sru, .srw)
Full source analysis — complete extraction
Binary Workspace
.pbl entries are binary files
Limited to config/metadata files — export PBLs for complete analysis
The agent auto-detects the format and reports it to you before proceeding.
From Exported Solutions (full analysis):
DataWindow definitions → domain entities with attributes and relationships
Window scripts → features (CRUD operations, navigation)
User objects → services and utilities
Menu/RibbonBar → module and feature structure
Config files → database connection, settings
Post-COMMIT calls → events and subscribers
From Binary Workspaces (limited):
Library list from .pbt → module boundaries
Config files, RibbonBar XML, theme JSON, README
Database schema (if DB access available)
For complete extraction, provide database access via one of:
Connection string in the prompt
Config.ini in the PB app folder (auto-discovered)
"No database access available" for artifact-only mode
With DB access, the agent performs FK chain analysis to discover all related entities, junction tables, and lookup tables.
General migration: Legacy Migration → Markdown
SP extraction: Stored Procedure & Trigger Extraction
JSON generation: Legacy Migration → JSON
Last updated