Hubbry Logo
PowerBuilderPowerBuilderMain
Open search
PowerBuilder
Community hub
PowerBuilder
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
PowerBuilder
PowerBuilder
PowerBuilder
View on Wikipedia
from Wikipedia
Appeon PowerBuilder
DeveloperSAP/Appeon
Initial releaseJuly 1992
Stable release
PowerBuilder 2025 / May 7, 2025
Preview release
None
Written inC++ and C#
Operating systemMicrosoft Windows
Available inEnglish, Japanese for the IDE (numerous languages supported for deployed applications)
TypeIDE
LicenseCommercial
Websitewww.appeon.com Edit this on Wikidata

PowerBuilder is an integrated development environment owned by SAP since the acquisition of Sybase in 2010. On July 5, 2016, SAP and Appeon entered into an agreement whereby Appeon, an independent company, would be responsible for developing, selling, and supporting PowerBuilder.[1]

Over the years, PowerBuilder has been updated with new standards. In 2010, a major upgrade of PowerBuilder was released to provide support for the Microsoft .NET Framework.[2] In 2014, support was added for OData, dockable windows, and 64-bit native applications.[3] In 2019 support was added for rapidly creating RESTful Web APIs and non-visual .NET assemblies using the C# language and the .NET Core framework. And PowerScript client app development was revamped with new UI technologies and cloud architecture.[4] In 2025 the IDE was revamped with new code editor and ultra-fast compiler.[5]

Appeon has been releasing new features every 6-12 month cycles, which per the product roadmap focus on four key focus areas: sustaining core features, modernizing application UI, improving developer productivity, and incorporating more Cloud technology.[6]

Features

[edit]

PowerBuilder has a native data-handling component called a DataWindow, which can be used to create, edit, and display data from a database. This object gives the programmer a number of tools for specifying and controlling user interface appearance and behavior, and also provides simplified access to database content and JSON or XML from Web services. To some extent, the DataWindow frees the programmer from considering the differences between Database Management Systems from different vendors. DataWindow can display data using multiple presentation styles and can connect to various data sources.

Usage

[edit]

PowerBuilder is used primarily for building business-oriented CRUD applications.

Although new software products are rarely built with PowerBuilder, many client-server ERP products and line-of-business applications built in the late 1980s to early 2000s with PowerBuilder still provide core database functions for large enterprises in government,[7][8][9] higher education,[10] manufacturing, insurance, banking,[11] energy, and telecommunications.

History

[edit]

Early history

[edit]

PowerBuilder originated from Computer Solutions Inc. (CSI), a software consulting firm founded in 1974 by Mitchell Kertzman in Massachusetts.[12][circular reference][13] CSI developed GrowthPower, an MRP II software package with integrated financial modules released in 1981, which ran exclusively on the HP 3000 platform and achieved over 1,000 customer installations at its peak.[14]

In the late 1980s, as demand increased for graphical user interfaces amid the rise of Microsoft Windows, Kertzman partnered with Dave Litwack, former executive vice president of product development at Cullinet Software (acquired by Computer Associates in 1989).[15][16] Litwack joined the company in 1988 as head of research and development to develop a client/server GUI tool, leading to its rebranding as Powersoft Corporation in 1990.[17][18]

PowerBuilder 1.0 was released in July 1991 as a rapid application development tool featuring the DataWindow and PowerScript language.[19] Powersoft went public on February 3, 1993, with shares closing at $38 from an initial $20 price.[20]

Sybase announced its acquisition of Powersoft on November 15, 1994, in a stock swap valued at approximately $940 million; the merger closed on February 14, 1995, at a revised value of about $904 million due to Sybase's stock fluctuations.[21][22][23][24]

Recent history

[edit]

In December 2013 SAP announced the new version going directly to number 15 and released a beta version.[25] Key features included support for the .NET Framework v4.5, SQL Server 2012, Oracle 12, Windows 8, OData and Dockable Windows. SAP later released this as version 12.6.

On May 31, 2019 PowerBuilder 2019 was released by Appeon. This release supports C# development. It provides a new C# IDE, .NET data access objects, C# migration solution, Web API client, and UI themes.[26]

On April 3, 2020 PowerBuilder 2019 R2 was launched by Appeon. This release includes a first-ever PowerScript-to-C# code converter, which can automatically migrate 80-95% of PowerBuilder business logic and DataWindows to C#.[27] Interoperability between PowerScript and .NET programming languages is also now supported. Many existing features have also been enhanced.

On January 22, 2021 PowerBuilder 2019 R3 was launched by Appeon. This release provides a groundbreaking new app deployment technology called PowerClient, which securely automates the installation and update of client apps over HTTPS. C# Web API development has been greatly enhanced with asynchronous programming and support for Amazon Aurora and Azure cloud databases. Aside from many other new features, PowerBuilder 2019 R3 is a long-term support (LTS) version that replaces previous LTS versions[28]

On August 6, 2021 PowerBuilder 2021 was launched by Appeon. The Cloud deployment capability of the PowerBuilder 2021 IDE, in conjunction with the matching PowerServer 2021 runtime, was revamped, bringing PowerBuilder up-to-date with the latest .NET technologies. The presentation layer now executes PowerScript natively on Windows devices. The middle-tier has been rebuilt around REST API standard with a pure .NET Core implementation. A new CI/CD utility that integrates with Git/SVN and Jenkins, witch compiles all PowerBuilder projects using the command-line interface, was added alongside other features.[29]

On September 4, 2022 PowerBuilder 2022 was launched by Appeon. This release brings enhancements to the productivity of developing both client/server & installable cloud apps and more security measures to safeguard your apps. It includes many new features, including Windows 11 support, introducing time-saving functionalities to the IDE, such as Tabbed Code Editor, Jump to Objects, and Quick Code Search, and supports the latest HTTP/2 and TLS 1.3 protocols and two-way TLS authentication.[30]

On August 4, 2023 PowerBuilder 2022 R2 was launched by Appeon. This release introduces a range of new features aimed at helping developers build powerful, feature-rich, and secure client/server and installable cloud apps more efficiently, including tabbed windows, fillable PDFs, and SMTP client.[31]

On January 8, 2024 PowerBuilder 2022 R3 was launched by Appeon. This release is a long-term support version. Features previously released in earlier releases have been enhanced and/or corrected.[32]

On May 7, 2025 PowerBuilder 2025 was launched by Appeon. This release delivers a revamped IDE that boosts developer productivity throughout the SLDC—from writing and extending code to debugging, automating builds, and deploying applications. It features a new-generation code editor, ultra-fast compiler, automatic REST API creation, faster GIT operations, and codeless UI modernization features.[5]

Features

[edit]

PowerBuilder is an object-oriented programming language. Nearly all of the visual and non-visual objects support inheritance, polymorphism, and encapsulation. The programmer may utilize a common code framework such as PowerBuilder Foundation Classes, also known as PFC, to inherit objects from and leverage pre-existing code.[33]

The DataWindow is the key component (and selling point) of PowerBuilder. The DataWindow offers a visual SQL painter which supports outer joins, unions and subquery operations. It can convert SQL to visual representation and back, so the developer can use native SQL if desired. DataWindow updates are automatic — it produces the proper SQL at runtime based on the DBMS to which the user is currently connected. This feature makes it easier for developers who are not experienced with SQL.

The DataWindow also has the built-in ability to both retrieve data and update data via stored procedures or REST Web APIs as well as import/export JSON data. The RESTClient object introduced in PowerBuilder 2017 facilitates bridging the DataWindow with REST Web APIs and requiring minimal coding.[34]

RDBMS interfaces

[edit]

PowerBuilder offers native interfaces to all major databases, as well as ODBC and OLE-DB, in the Enterprise version. There are many connectivity options that allow performance monitoring and tuning, such as:

  1. Integrated security
  2. Tracing of all SQL
  3. Isolation level
  4. Password expiration dialog
  5. Blocking factor
  6. Number of SQL statements to cache
  7. Use connection pool
  8. Thread safety
  9. Trace ODBC API calls

Due to the information about the database schema (such as primary key information) that are stored in PowerBuilder's data dictionary, the code required to implement data display and browsing is greatly simplified, because the dictionary information allows generation of the appropriate SQL behind the scenes.

PowerBuilder supports the following ways of interacting with a database:

DataWindow: this is the simplest approach, relying on automatically generated SQL.

"Embedded SQL"
Embedded SQL supports SELECT, INSERT, UPDATE, DELETE and cursors. This option is used when the developer desires more control than is available with the DataWindow option. Example:
 UPDATE my_employee SET STATUS = 'A';
 IF sqlca.sqlcode<>0 THEN ...
"Dynamic SQL"
This is a form of parameterized SQL, where the user builds a string that may optionally have bind variables. Dynamic SQL may be used to create cursors as well.

Integration with third-party software

[edit]

PowerBuilder supports ActiveX and OCX controls, both visible and non-visible. It also can use OLE Automation as a client. However, PowerBuilder supports only late binding, not early binding. Therefore, when using OLE Automation, a dropdown of possible actions is not provided. PowerBuilder can also act as a DDE client or server, providing a further mechanism to interoperate with other applications.

PowerBuilder can make Windows and third-party API calls, and, in general, works well with third-party libraries in DLL files, however it does not directly support callback functions.

Compilation and debugging

[edit]

PowerBuilder offers a "/pbdebug" (or variants: "-pbdebug", "-pbd", "/debug", "-debug", "-deb") runtime switch, which creates a log file. This can help track down a bug "in the field", as the user simply emails this log file to the developer. It has another feature which can log all SQL statements to a file. It also has built-in performance profiling, an integrated debugger, context-sensitive help, and an active newsgroup to provide support.

PowerBuilder applications are typically compiled to p-code, which is then interpreted by the PowerBuilder runtime environment. An application can also be compiled to machine code, which can sometimes offer a performance benefit.

Criticism

[edit]

Extensibility of the language was rather limited for older versions of PowerBuilder. To develop a solution that includes external C++ code may not only require a competent C++ developer, but also a PowerBuilder expert to guide the developer through the myriad subtleties of the language and the PowerBuilder Virtual Machine.

Inheritance and object-oriented features are limited to some object types (Windows, Userobjects and Menus). In particular, it is not possible to inherit from a DataWindow. A PowerBuilder user cannot open a descendant and a parent at the same time in the painter, though they can see all ancestors' code while working on the descendant.

To address these criticisms, Appeon has set a new roadmap for PowerBuilder, which it publishes openly on the Appeon Website.[35] Amongst developers, the (classic) PowerScript language itself, which is still available for compatibility reasons, is known as a "language built around the DataWindow", and PowerBuilder is known as the "IDE built around the DataWindow". C# development centered around a new .NET DataWindow with automated migration of existing DataWindows was introduced in PowerBuilder 2019.[36]

Community

[edit]

Since Appeon took over PowerBuilder, it has launched a new official community website for PowerBuilder developers. This community website offers technical articles, webinars, and Q&A, which are authored by community users. Appeon also hosts an annual user conference called Appeon Elevate, and recordings of the conference sessions are available from the conference website. There are a number of local user groups around the world that cooperate with Appeon to deliver abridged versions of the conference in seminar format and local language. [37]

There are also a variety of grassroots community groups and resources for PowerBuilder developers to share and convene. PowerBuilderTV[38] is series of webinars by PowerBuilder users and vendors that tend to focus on third party add-ons. PowerBuilder Central[39] is a community initiative to create a single source for third party add-ons and services.

PowerBuilder Tools

[edit]
  • Appeon PowerServer - Deploys existing or new PowerBuilder projects as cloud-native applications that runs on .NET Core with support for almost every single PowerBuilder feature, including the PFC framework.[40]
  • Visual Expert for PowerBuilder - Visual Expert helps in sharing the knowledge of your applications. It also automates impact analysis and checks code quality.[41]
  • Enable Multilingual - Enable makes PowerBuilder applications multilingual quickly and easily. Using Enable, developers can only need to make a few small changes to the original PowerBuilder code to go from monolingual to multilingual.[42]
  • ProDiff for PowerBuilder - ProDiff is designed to highlight the differences between versions of PowerBuilder development source code.[43]
  • Visual Guard for PowerBuilder - Visual Guard is an access control and application-level permissions tool. It helps you centralize view and control of users and their rights in PowerBuilder applications.[44]
  • STD Framework for PowerBuilder - A free object-oriented development framework for PowerBuilder Classic, Web Services, Appeon PowerServer Web and Mobile.[45]
  • Ultimate Suite for PB - A suite of controls, written in PowerScript, that modernizes the GUI of PowerBuilder applications; Ultimate Suite for PB gives applications a contemporary look and makes them more user-friendly.[46]
  • AscentialTest - Automated testing for PowerBuilder, web, and others. Deep integration with the PowerBuilder VM api's allow AT to see and understand PB objects.
  • PowerGen - Automated build and regeneration of PowerBuilder applications. Supports building directly from Source Control.[47]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

PowerBuilder

View on Grokipedia
from Grokipedia
PowerBuilder is a (RAD) tool designed for building object-oriented client/server, n-tier, and web applications, featuring an (IDE) that emphasizes productivity through visual design, scripting in PowerScript, and advanced data handling via its proprietary DataWindow technology. Originally developed by Powersoft, PowerBuilder was first released in July 1991 as version 1.0, quickly gaining popularity for enabling developers to create data-driven business applications efficiently in the emerging client-server computing era. In November 1994, Sybase acquired Powersoft for approximately $940 million, integrating PowerBuilder into its portfolio as a development tool while allowing Powersoft to operate initially as an independent subsidiary. Following 's acquisition of Sybase in 2010, PowerBuilder became part of SAP's offerings, with version 12.6 released in 2014 as the final major update under direct SAP development. In July 2016, SAP entered into an agreement with Appeon, granting the company rights to develop, sell, and support a new generation of PowerBuilder, marking a shift toward modernization with enhanced support for cloud deployment, APIs, and contemporary user interfaces. Under Appeon, key advancements include a revamped IDE with a faster (up to 2-3 times quicker), codeless UI theming, automatic API generation, and compatibility with modern databases like SQL Server, , and , alongside support for and TLS 1.3 security. The platform follows a release cycle of every 10-12 months, with the latest version, PowerBuilder 2025, focusing on streamlined development workflows, binary-to-source file conversion for better , and seamless migration from legacy versions. PowerBuilder's enduring strengths lie in its visual painters for forms and reports, robust , and tight integration with relational databases, making it particularly suited for enterprise applications in industries such as , healthcare, and , where and are critical. Despite competition from web-centric frameworks, it retains a dedicated user base for modernizing legacy systems into hybrid cloud environments.

History

Origins and Early Development

Powersoft Corporation, originally founded in 1974 as Computer Systems Integrators by Mitchell Kertzman, shifted its focus in 1988 toward developing client-server application tools amid the rising popularity of personal computers and Windows environments. This pivot led to the creation of PowerBuilder, a pioneering (RAD) platform designed to streamline the building of database-driven applications. By leveraging visual programming paradigms, Powersoft aimed to empower developers to create robust client-server solutions without extensive manual coding, targeting the growing demand for SQL-integrated . PowerBuilder 1.0 was released on July 1, 1991, marking a significant advancement in Windows-based development by introducing intuitive visual painters for designing forms and reports, alongside native SQL support for database connectivity. A cornerstone feature was the debut of the technology, a declarative control that enabled seamless binding of from relational databases to user interfaces, allowing developers to generate dynamic reports and editable grids with minimal scripting. This RAD approach, combined with PowerScript—a event-driven language—positioned PowerBuilder as an efficient tool for enterprise applications, quickly gaining traction among developers transitioning from mainframes to distributed systems. Subsequent releases built on this foundation, with PowerBuilder 2.0, launched in June 1992, further enhanced the platform by introducing object-oriented inheritance for reusable components and expanded database interfaces, including improved support for SQL Server and . These updates facilitated more scalable and modular application design, solidifying PowerBuilder's role in team-based development. Powersoft experienced rapid growth during this period, selling over 8,000 copies of PowerBuilder by early 1993 and projecting $25 million in revenue for 1992, which underscored its emergence as a market leader in fourth-generation language (4GL) tools for client-server environments. The company's successful on February 3, 1993, raised $71 million at $20 per share, with stock nearly doubling on the first , reflecting strong confidence in PowerBuilder's innovative . This financial milestone enabled further investment in the product's evolution, setting the stage for broader enterprise adoption.

Sybase Ownership Period

In November 1994, Sybase announced its acquisition of Powersoft Corporation, the creator of PowerBuilder, in a stock swap valued at approximately $940 million. The merger closed in February 1995, positioning PowerBuilder as a key component of Sybase's client-server ecosystem by enabling seamless integration with Sybase databases like for rapid development of database-driven applications. This move expanded PowerBuilder's reach, allowing Sybase to offer end-to-end solutions for enterprise computing, where PowerBuilder served as the front-end development tool complementing Sybase's technologies. During the Sybase era, PowerBuilder underwent significant technical advancements through major version releases that enhanced its enterprise capabilities. Version 5.0, released in 1996, introduced the PowerBuilder Foundation Classes (PFC) library, a set of reusable object-oriented components that accelerated development by providing pre-built services for , error handling, and consistency. Subsequent releases built on this foundation: version 6.0 in 1997 previewed web deployment options and included integration with Power++ Enterprise for C++ code generation, while version 9.0 in 2003 added robust XML support for data exchange in distributed environments. The lineup culminated in version 12.5 in 2011, which incorporated .NET framework compatibility for hybrid applications and migrated the IDE to the platform for improved extensibility and plugin support. Sybase emphasized enterprise-grade features to address needs, such as the integration of Jaguar Component Transaction Server (CTS) in , which enabled scalable n-tier architectures using CORBA for component-based deployment of PowerBuilder applications. This allowed developers to build and manage server-side components that interfaced with PowerBuilder clients, supporting high-volume in multi-tier setups. Despite these innovations, PowerBuilder faced market challenges in the late from emerging Java-based tools, which gained traction for cross-platform web applications amid the dot-com boom. Nevertheless, PowerBuilder maintained strong adoption in and sectors, where its reliability for mission-critical, database-intensive applications proved enduring, powering systems at organizations like major banks and federal agencies.

SAP Acquisition and Appeon Partnership

In 2010, acquired Sybase for $5.8 billion, bringing PowerBuilder into its portfolio as a key tool for enterprise application development. This move integrated PowerBuilder's client-server capabilities with 's broader ecosystem, emphasizing its role in building scalable business applications. Under SAP's ownership, PowerBuilder saw the release of version 12.6 in , which introduced OData support, 64-bit applications, and expanded platform compatibility including Oracle 12c. However, direct investment in PowerBuilder declined as SAP prioritized its proprietary tools, such as SAPUI5 and Fiori, leading to version 12.6 as the final major release from and a shift away from active innovation in the product. In 2016, SAP entered a licensing agreement with Appeon, granting the company rights to develop, sell, and innovate PowerBuilder, ensuring its continued evolution beyond SAP's primary focus. Appeon subsequently released version 2017 in June 2017, which added support for RESTful APIs to enable modern web services integration, followed by version 2019 in May 2019 with C# development support, version 2021 in December 2021 enhancing security and productivity, and version 2022 in September 2022 introducing features and IDE improvements. Appeon's stewardship has emphasized modernization, particularly through PowerServer, a cloud deployment platform that allows PowerBuilder applications to run as web and mobile apps while preserving with legacy codebases built on earlier versions like 12.6. In 2025, PowerBuilder received significant updates with version 2025 released on May 7, 2025, including a revamped (IDE) with a new code editor for enhanced productivity, an ultra-fast multi-threaded compiler, automatic generation from DataWindows, and codeless UI theming options to simplify interface customization. A maintenance release followed on November 12, 2025, adding high DPI support and improved connectivity via . These advancements position PowerBuilder for contemporary enterprise needs, such as cloud-native scalability, without disrupting existing deployments.

Core Components

PowerScript Programming Language

PowerScript is a high-level, language integral to PowerBuilder, designed to facilitate by blending procedural and object-oriented paradigms with a syntax reminiscent of . It enables developers to write scripts that respond to user interactions and system events, supporting both standalone procedural code and integration within an object-oriented framework. At its core, PowerScript employs where scripts are associated with specific events on controls and objects. For instance, the clicked() event triggers when a user clicks a , allowing code to execute in response, such as validating input or updating displays. Similarly, the open() event fires upon the initialization of a or , providing an opportunity to set initial properties or load data. This mechanism supports over 149 predefined events, each with arguments like coordinates or return codes to inform the script of contextual details. PowerScript includes built-in system objects that simplify common operations. The Message object captures details of Windows events not natively defined in PowerBuilder, such as low-level system notifications, enabling custom handling of mouse movements or keyboard inputs. The Transaction object serves as the communication link between the application and databases, managing connections, SQL execution, and error states through properties like SQLCode and SQLErrText. The language supports a range of standard data types to handle diverse data needs. Blobs store unbounded , such as images or raw files, without size limits beyond memory constraints. Date types represent dates from the year 1000 to 3000, using literals in YYYY-MM-DD format (e.g., 2001-12-25). types accommodate signed numbers with up to 28 digits of precision, ideal for financial calculations, with literals like 12.34 or -6500. Other types include booleans for true/false logic, bytes for 8-bit unsigned integers (0-255), characters for single Unicode symbols, and strings for variable-length text up to approximately 1 GB. Control structures in PowerScript provide familiar constructs for logic and flow. Conditional execution uses IF...THEN...ELSEIF...ELSE...END IF to branch based on boolean expressions. Loops include FOR for fixed iterations (e.g., FOR i = 1 TO 10), DO WHILE for condition-based repetition until false, and DO UNTIL for continuation until a condition holds true. Exception handling employs TRY...CATCH...FINALLY...END TRY to gracefully manage runtime errors, with the CATCH block processing specific exceptions and FINALLY ensuring cleanup regardless of success. PowerScript integrates seamlessly with SQL for database interactions, supporting both embedded and dynamic approaches. Embedded SQL allows direct inclusion of statements like SELECT, INSERT, UPDATE, and DELETE within scripts, using colon-prefixed variables (e.g., INSERT INTO EMPLOYEE (SALARY) VALUES (:Sal_var);) to bind PowerScript variables to SQL parameters. Indicator variables, such as :IndVar1, detect nulls (-1) or conversion errors (-2), enhancing data integrity. For flexibility, dynamic SQL uses cursors declared with DECLARE Emp_cur CURSOR FOR SELECT... and manipulated via OPEN, FETCH, and CLOSE statements, or stored procedures invoked with DECLARE...PROCEDURE FOR and EXECUTE. These operations typically leverage the Transaction object for connection management. Introduced with PowerBuilder 1.0 in 1991 as a basic scripting tool for client-server applications, PowerScript has evolved to support modern development needs, with enhancements in later versions focusing on improved syntax flexibility, handling, and integration capabilities. By PowerBuilder 12.0, it incorporated enhancements for better .NET compatibility, and recent releases like 2025 introduce new functions in the Application object for cloud-specific tasks, such as management in installable cloud apps, alongside refined error handling in runtime environments.

Object-Oriented Framework

PowerBuilder employs a class-based model that enables developers to create modular and reusable applications through inheritable classes such as windows, menus, user objects, and controls. These classes encapsulate both and , allowing for the construction of complex systems with a focus on maintainability and extensibility. Visual classes like windows and menus support components, while user objects and controls provide building blocks for custom functionality, all inheriting from system-defined ancestors to promote . The hierarchy in PowerBuilder is structured around -descendant relationships, where descendant objects can extend or modify behaviors through and polymorphism achieved via dynamic dispatching. Developers can create a chain of , for instance, deriving a custom from a standard and then further specializing it in subsequent , ensuring consistent implementation across the application. Polymorphism allows functions with the same name to exhibit different behaviors based on the object type or level, supporting both operational polymorphism (via ) and inclusional polymorphism (through ). This mechanism facilitates flexible, type-safe code that adapts at runtime. Encapsulation is enforced through access modifiers—private, protected, and —along with that enable hiding and controlled interaction between objects. Private and protected members restrict direct access to internal state, exposing only necessary interfaces via methods or , which helps maintain object integrity and reduce in large applications. For example, a user object might define private instance variables for sensitive , accessible only through getter and setter functions, promoting the principle of . Non-visual objects, such as standard class user objects and custom non-visual user objects, are designed to encapsulate and services without a graphical interface, allowing for the in application design. These objects handle tasks like , transaction management, and validation, often instantiated dynamically to support modular architectures. Complementing this, global functions serve as utility methods accessible across the application, providing shared operations without the overhead of object instantiation. The PowerBuilder Foundation Class (PFC) library extends the core object-oriented framework by offering a collection of reusable, inheritable classes and services that implement standardized patterns for common application needs, including error handling and security. Developed originally by Sybase, PFC includes concrete objects for windows and data services, as well as abstract service classes that can be inherited and customized, ensuring consistent error propagation through exception services and role-based access control via security services. This framework leverages PowerBuilder's inheritance and encapsulation to reduce development time while enforcing best practices for robust, scalable applications.

DataWindow Technology

The DataWindow serves as PowerBuilder's core technology for handling data presentation, manipulation, and reporting, functioning as a composite control that integrates a data source—typically SQL queries or stored procedures—with various presentation styles and embedded scripting capabilities. A DataWindow object defines the layout and logic, including the data retrieval syntax and visual elements like columns, labels, and graphics, while the DataWindow control embeds this object into a window or for runtime interaction. This separation allows developers to design reusable objects in the DataWindow painter and associate them with controls via PowerScript, enabling dynamic data handling without custom coding for basic operations. Data binding in the DataWindow occurs through methods like Retrieve, which fetches rows from the database using specified arguments to parameterize queries, such as filtering by user input or date ranges. Updates are managed via the Update method, which applies changes from the DataWindow's buffers—primary for current data, filter for temporary subsets, and delete for removed rows—generating SQL statements with WHERE clauses to target only modified records and prevent overwriting unrelated data. This buffering mechanism supports by storing changes locally until explicitly committed, reducing database round-trips and enhancing performance in disconnected scenarios. Built-in presentation styles include Grid for editable tabular views, Tabular for fixed reports, and Graph for visual summaries, each customizable with expressions for computed fields that derive values like sums or concatenations from other columns. Validation rules enforce using expressions, such as checking numeric ranges or required fields, while conditional formatting applies styles like bold text or color changes based on data values, all defined in the DataWindow painter without external code. These features leverage PowerScript for runtime adjustments, allowing expressions like If(GetItemNumber(1) > 100, "High", "Low") in computed fields. Export and import functionalities enable seamless data exchange, with the SaveAs method supporting formats like PDF for printable reports and Excel for spreadsheet integration. PowerBuilder 2025 introduces the SaveDisplayedDataAs method, which exports displayed data values (such as formatted text from Edit columns) to Excel, though without support for advanced visual elements like fonts, borders, or graphical objects. ImportFile loads data from CSV, tab-delimited text, or Excel files via OLE automation, populating the DataWindow buffers for further manipulation. For visualization, the Graph style integrates charts like bar or pie representations directly from DataWindow data, with options to customize axes and legends through properties. Advanced capabilities extend the DataWindow's versatility, including the Crosstab style for dynamic pivot tables that aggregate data across rows and columns based on runtime values, and Freeform layouts for flexible, label-adjacent designs suitable for forms or invoices. In PowerBuilder 2025, enhancements include improved update property persistence, where settings in the Specify Update Properties dialog are retained when modifying updatable tables in DataWindow SQL (e.g., adding or deleting columns), helping prevent during migrations, alongside enhanced high-DPI support for the UI including DataWindow controls, though with limitations such as potential blurriness in images and sizing issues during dynamic DPI changes. These features can be extended via the object-oriented framework by inheriting from base DataWindow objects to customize behaviors like event handling.

Development Environment

Integrated Development Environment

The PowerBuilder (IDE) organizes application development around a central workspace, now referred to as a solution in version 2025, which encapsulates and projects to manage the overall structure of an application. The Library Painter serves as a key component for managing libraries (PBL files), enabling developers to create, copy, move, delete, and organize objects such as and menus within these repositories. Complementing this, the integrated Browser facilitates searching across , libraries, and objects by allowing users to select scopes and query for strings in properties, scripts, or variables, with results displayed in an Output for quick navigation. Project objects, defined in the Project Painter, handle build configurations by specifying names, dynamic libraries, files, and options like code generation type (Pcode or ) and platform targeting (32-bit or 64-bit). Visual designers within the IDE streamline and data handling tasks. The Window Painter provides views for laying out forms, setting properties for windows and controls, and scripting behaviors, resembling a stacked workspace with Script and Properties panes. Similarly, the Menu Painter offers Tree Menu and views to build hierarchical menus and toolbars, supporting styles like contemporary (3D with images and animations) or traditional (flat), along with property tabs for item-specific configurations. For extract-transform-load (ETL) operations, the Data Pipeline Painter allows creation of pipelines to reproduce and manipulate database data into reports, forms, or other outputs. Code editing in the IDE centers on PowerScript, the primary programming language, with features like syntax highlighting and auto-completion integrated into the workflow for scripting objects. PowerBuilder 2025 introduces a revamped modern code editor with enhanced syntax highlighting (configurable colors for functions, variables, and classes), intelligent context-aware auto-completion via improved AutoScript, support for themes through customizable coloring and zooming, and refactoring tools including multi-cursor editing, case conversion, and code folding. These updates also include bracket matching, line numbers, and advanced find/replace with regular expressions to boost productivity. Version control integration has evolved to natively support in PowerBuilder 2025, allowing developers to add solutions to repositories, commit changes, retrieve objects, resolve conflicts, and revert modifications directly within the IDE, alongside continued SVN compatibility. This facilitates multi-target development for desktop, web, and cloud deployments without external plugins. System requirements for the IDE have progressed from compatibility with in early versions to robust support in 2025 for and 11 (32-bit and 64-bit), requiring a minimum of an or processor with 4 cores at 1.8 GHz, 8 GB RAM (16 GB recommended), and 4 GB hard drive space. The 2025 release adds full high-DPI awareness for crisp rendering on high-resolution and setups, ensuring scalability from legacy environments to modern hardware.

Compilation and Debugging Tools

PowerBuilder supports two primary compilation modes: P-code, which generates interpreted stored in PowerBuilder dynamic (PBD) files, and , which produces native executables () or dynamic link libraries (DLL) for faster runtime . The PowerBuilder Compiler (PBC), a command-line tool such as PBC250.exe in PowerBuilder 2025, facilitates both modes by compiling objects defined in the . In the latest versions, P-code is the default and is unsupported in the solution-based format, automatically converting projects to P-code during migration. Build automation in PowerBuilder relies on project objects to configure compilation targets, enabling full builds that regenerate all objects or incremental builds that recompile only modified objects and their dependencies to optimize development cycles. PowerBuilder 2025 introduces an ultra-fast compiler for solution-format projects, leveraging plain-text source code to achieve 2-3 times faster full builds compared to traditional PBL-based compilation, with incremental builds benefiting from multi-threaded processing. The PBAutoBuild250.exe tool extends this automation for and (CI/CD) pipelines, allowing command-line execution of builds and deployments, often integrated with systems like Jenkins for automated workflows. Debugging tools in PowerBuilder enable developers to set breakpoints at specific lines or conditions, monitor watch variables for real-time value changes, and perform step-through execution modes such as step into, , or step out to trace code flow. The also provides tracing to inspect the execution hierarchy and variable scopes during runtime sessions, with breakpoints and watches persisted across sessions via user option files. These features operate within the IDE's views, supporting both P-code and applications for iterative testing. Profiling tools in PowerBuilder generate trace files during application execution to analyze bottlenecks, capturing metrics on routine calls, object interactions, and execution timelines through views like Class View, Routine View, and Trace View. SQL tracing integrates with database connections to log query execution details, helping identify slow statements or connection issues without external tools. For detection, trace analysis can reveal unreleased object allocations, though specialized third-party tools may supplement built-in capabilities for deeper inspection. Error handling in PowerBuilder utilizes the RuntimeError object, which inherits from Throwable and encapsulates runtime exceptions with properties for error numbers, messages, and stack traces, allowing developers to catch and process s via try-catch blocks. Logging frameworks can be implemented using PowerScript to record error details to files or databases, with open-source libraries like EXF providing structured exception management and extensions.

User Interface Design Capabilities

PowerBuilder provides robust visual design tools through its integrated painters, enabling developers to create intuitive user interfaces without extensive coding. The primary tool for UI design is the Window painter, which offers a graphical Layout view for constructing windows and placing controls. Developers can various controls—such as buttons, list boxes, tab controls, and edit fields—from the System Tree or toolbox directly onto the layout canvas, facilitating and . Once placed, controls support extensive property customization in the Properties view, including alignment options (e.g., left, right, center), sizing behaviors, and event handling for user interactions like clicks or resizing. For instance, properties such as TabOrder ensure logical navigation flow, while alignment settings maintain consistent layouts across different window states. Events can be scripted in the integrated Script editor to define behaviors, such as validating input or updating displays dynamically. These features allow for precise control over UI elements, promoting reusable and maintainable designs. In PowerBuilder 2025, responsiveness is enhanced through features like auto-sizing controls that adapt to window resizes via properties such as FixedTo or script-driven adjustments, and docking mechanisms for anchoring elements to window edges—though traditional dockable windows are deprecated in favor of modern alternatives. The RibbonBar control introduces responsive layouts that automatically adjust tabs, groups, and buttons based on available screen space, supporting fluid interfaces on varying display sizes. Codeless UI theming further bolsters adaptability, allowing CSS-like styling (e.g., colors, borders, fonts) to be applied via configuration files or built-in wizards without altering underlying code. Multi-device support includes Multiple Document Interface (MDI) windows for managing multiple child windows within a parent frame, tabbed MDI for compact navigation, and RibbonBar integration introduced in version 2019 and refined in 2025 for ribbon-style menus. These elements enable touch-friendly layouts with larger, gesture-optimized controls and DPI-aware rendering for high-resolution and environments, ensuring consistent performance across desktops, tablets, and hybrid setups. DataWindow controls integrate seamlessly for data-driven UI displays, embedding dynamic tables or graphs with minimal configuration. Accessibility is addressed through compliance with standards, making PowerBuilder controls compatible with screen readers like Windows Narrator for auditory feedback on UI elements. Keyboard navigation is supported natively via standard Windows conventions, with properties like TabOrder and Enabled ensuring sequential focus traversal and interactive for users relying on assistive technologies. Theming and skinning capabilities in PowerBuilder 2025 extend to built-in UI themes, such as Blue, Dark, Grey, and Silver, which can be applied globally or per-control to modernize appearances with flat aesthetics and customizable palettes. Developers can create custom themes using external libraries or the Theme wizard, editing files for skin-like effects including gradients, shadows, and hover states, all while maintaining with legacy applications.

Deployment and Integration

Traditional Client-Server Deployment

PowerBuilder's traditional client-server deployment model centers on creating desktop applications that run as thick clients on user machines, directly to backend databases for data processing and execution. This approach, prevalent since the tool's early versions, emphasizes standalone executables that leverage the PowerBuilder (PBVM) to interpret compiled P-code, enabling efficient runtime performance without requiring the full development environment on client systems. To generate deployable artifacts, developers use the PowerBuilder IDE's project painter to build standalone (EXE) files or dynamic-link libraries (DLLs) from application targets, incorporating libraries in PBD (PowerBuilder Dynamic Library) or DLL formats for modularity. These outputs rely on runtime files, including the core pbvm.dll, which executes the application's P-code—a format that PowerBuilder compiles source into for platform-independent interpretation and optimized execution. Supporting DLLs such as pbshr.dll (for shared runtime functions) and pbdwe.dll (for DataWindow ) must also be included, ensuring the application can handle rendering and data manipulation locally on Windows clients. In the client-server architecture, these thick client applications establish direct connections to relational databases like or using standard interfaces such as ODBC or JDBC, facilitated by the client's local driver manager and database-specific drivers. ODBC connections, for instance, follow a multi-tier model where the PowerBuilder application communicates through the ODBC Driver Manager to the DBMS driver and ultimately the data source, supporting both ANSI and data handling for robust two-tier operations. This setup allows for retrieval and updates, with the client bearing the computational load for UI and logic while the server manages and queries. For distribution, PowerBuilder provides the Runtime Packager tool to bundle the EXE, required DLLs, and resources into a package, simplifying end-user installation via wizards that handle file placement and registry entries. Runtime files like pbvm.dll are freely distributable without additional licensing fees, though version-specific dependencies necessitate matching the exact PowerBuilder runtime version (e.g., 2022) to avoid compatibility issues, often managed through an tied to the executable. Resources such as bitmaps or icons can be embedded via a PowerBuilder Resource (PBR) file or deployed separately to reduce executable size. Security in traditional deployments typically involves INI files, such as pbodb.ini, to store database connection parameters like server names, user IDs, and passwords, which are read by the application at startup and placed in the same directory as the runtime DLLs or referenced via registry paths. Basic options, like the Encrypt parameter for certain native interfaces, can secure sensitive data in transit, but overall protection relies on standard DBMS and lacks advanced features for remote access. Prior to the introduction of PowerServer, this model exhibited limitations in scalability for web-based access, as applications were confined to local or LAN environments, requiring physical client installations and struggling with remote or browser-based delivery due to the desktop-centric thick client design.

Modern Web and Cloud Deployment

PowerServer, introduced by Appeon in 2019 alongside PowerBuilder 2019, enables cloud-native deployment of PowerBuilder applications by converting traditional client/server apps into RESTful web services paired with / frontends. This approach allows existing PowerBuilder codebases to be modernized without full rewrites, transforming them into web-accessible applications that run on standard web servers or cloud platforms. The deployment workflow begins with configuring a PowerServer project in the PowerBuilder IDE, where developers select app components for deployment and specify server settings. PowerServer then automatically generates REST APIs from the PowerBuilder , packages the client-side as a lightweight /JS app, and supports containerization via Docker for streamlined distribution. These containers can be orchestrated with for scalable environments, and the resulting artifacts are deployable to major cloud providers such as AWS or Azure, often using managed services like Azure Container Instances or AWS Elastic Container Service. This process facilitates seamless migration from legacy models by preserving PowerScript logic while enabling horizontal scaling and reduced infrastructure management. In 2025, PowerServer enhancements emphasize greater flexibility and faster deployment times through features like dynamic SQL support and optimized API generation, alongside improved scalability for handling high-traffic applications via enhanced .NET Core integration and load balancing in clustered setups. These updates build on prior versions by streamlining cloud orchestration, allowing applications to auto-scale based on demand without custom coding. For mobile extensions, PowerServer supports Progressive Web Apps (PWAs) for responsive web experiences across devices, enabling offline capabilities and adaptability to various screen sizes while maintaining a unified codebase. Licensing for PowerServer offers both subscription and perpetual options, with costs tied to concurrent user sessions for deployments, including clustered setups across multiple servers. This structure supports elastic cloud environments by allowing licenses to activate on various nodes while enforcing usage limits through session tracking.

Third-Party Software Integration

PowerBuilder offers robust database connectivity options, supporting native drivers for Sybase (ASE) and SQL Anywhere, which allow direct, high-performance access to these databases without requiring intermediary layers. For broader compatibility with other relational database management systems (RDBMS), it leverages standard interfaces such as ODBC and to connect to databases like , , and . These interfaces enable seamless data retrieval and manipulation in client-server architectures, with ODBC providing a standardized for diverse data sources and offering optimized access for Windows-based environments. Integration with web services is facilitated through built-in support for and protocols, allowing PowerBuilder applications to consume and interact with external APIs. Since PowerBuilder 2017, enhancements to the HTTPClient object have simplified RESTful service calls, including improved handling of and XML data parsing via dedicated functions like JSONParser and XMLDocument. These features support secure data exchange, with XML for structured messages and for lightweight REST responses, enabling applications to integrate with modern web-based services efficiently. For interoperability with other platforms, PowerBuilder provides bridges to .NET and ecosystems. .NET integration occurs through direct assembly calling with the DotNetAssembly and DotNetObject classes, alongside COM interop for legacy components, permitting PowerBuilder code to invoke .NET methods and handle events bidirectionally. connectivity is achieved via the PowerBuilder Native Interface (PBNI), which utilizes the (JNI) to enable communication between PowerBuilder virtual machines and applications, supporting custom extensions and shared functionality. In PowerBuilder 2025, OAuth 2.0 capabilities have been further refined with the object, enhancing secure authentication for cloud services like and using grant types such as client credentials and authorization code. Practical examples of third-party integrations include embedding modules, where PowerBuilder applications connect via APIs to for real-time data synchronization in business processes. Similarly, reporting tools like integrate through .NET components or the Crystal Reports Viewer control, allowing dynamic report generation and embedding within PowerBuilder interfaces for analytics and output formatting. These integrations highlight PowerBuilder's flexibility in extending enterprise applications with external tools while maintaining and performance.

Usage and Applications

Typical Use Cases

PowerBuilder is widely utilized for developing enterprise line-of-business applications that perform core CRUD (create, read, update, delete) operations, such as inventory management systems and platforms incorporating advanced reporting and data visualization features. These applications leverage PowerBuilder's integrated tools to streamline data handling and user interactions in two-tier client/server environments. In the industry, PowerBuilder supports the construction of robust applications. Such systems enable secure, high-volume data operations essential for banking and workflows. agencies and healthcare organizations frequently adopt PowerBuilder for data-intensive form-based applications in case , where the DataWindow technology delivers secure, customizable views of sensitive information while ensuring and access controls. This approach facilitates efficient handling of patient records or cases without compromising regulations. Migration scenarios represent another prominent use case, particularly for modernizing legacy client-server applications—often originating from mainframe or COBOL-based systems—to contemporary web architectures via PowerServer, allowing seamless transition while preserving existing . This method minimizes disruption and extends the lifespan of critical systems in resource-constrained environments. PowerBuilder's rapid application development (RAD) paradigm accelerates prototyping, enabling developers to build functional prototypes in days compared to months required by conventional low-level coding techniques, thereby reducing time-to-market for iterative enterprise solutions.

Industry Adoption and Case Studies

PowerBuilder achieved peak adoption during the , when it became a leading tool for client-server application development, with nearly one million developers worldwide by around 1997. Its rapid growth was driven by its productivity advantages in building database-driven applications, leading to widespread use among major corporations for enterprise systems. By the late , PowerBuilder powered critical business applications in numerous companies, establishing dominance in sectors requiring robust client-server solutions. Following the shift to web-based architectures in the early , PowerBuilder's declined as organizations migrated to newer platforms like and .NET, reducing the active developer base to an estimated 100,000 globally by the late . Despite this, many legacy applications remained in production, with some systems over 30 years old continuing to support core operations due to their stability and the high cost of rewrites. Under Appeon's stewardship since 2016, PowerBuilder has experienced a resurgence through modernizations like PowerServer for cloud and web deployment, attracting new adopters and revitalizing existing ones. Today, over 18,000 organizations use PowerBuilder, including most companies across industries such as , consulting, and . The platform maintains a strong presence in banking and utilities, where it supports mission-critical systems for and operations. Notable case studies highlight PowerBuilder's impact. AT&T leverages PowerBuilder for invoice management applications, enabling mobile access to streamline billing processes for millions of customers. In consulting, Accenture deployed a web-based enterprise product using PowerServer on , reducing deployment times and enhancing scalability for client solutions. For utilities, the nation's largest natural gas distribution company modernized over one million lines of PowerBuilder code to C#/.NET, preserving functionality while improving performance across 650+ screens and 3,300+ data windows. In banking, a leading New York financial institution re-engineered its system built in PowerBuilder, transitioning to a modern platform that reduced maintenance overhead and ensured compliance with evolving payment standards. Similarly, another major financial firm transformed multiple PowerBuilder applications to , achieving cost efficiencies and extended system longevity without disrupting daily transactions. These examples demonstrate PowerBuilder's enduring value in high-stakes environments, where migrations maintain reliability while often reducing operational costs.

Reception

Strengths and Advantages

PowerBuilder's (RAD) environment enables visual construction of user interfaces and data-driven logic, significantly reducing the lines of code needed compared to 3GL languages like or C#, which often require manual implementation of equivalent functionality. This efficiency stems from integrated tools such as the DataWindow painter, allowing developers to generate complex reports and forms with minimal scripting, thereby accelerating the overall development lifecycle by focusing on rather than . The DataWindow technology provides robust data handling capabilities, excelling in query retrieval and update operations by processing data in blocks instead of row-by-row, which delivers faster performance than manual grid controls in competing frameworks. This built-in optimization supports seamless integration with major relational databases like SQL Server, , and , minimizing custom coding for data manipulation and ensuring high-speed rendering of large datasets. PowerBuilder demonstrates exceptional , enabling applications from legacy versions such as PowerBuilder 6 through 12.6 to upgrade directly to the 2025 release with little to no code modifications, preserving decades of development investment without the need for extensive rewrites. This continuity supports uninterrupted operation across evolving Windows operating systems and hardware, reducing migration risks for long-standing enterprise systems. In terms of cost-effectiveness, PowerBuilder lowers the (TCO) for legacy applications by streamlining maintenance and upgrades, avoiding the high expenses associated with full platform rewrites while extending the lifespan of existing codebases. Enterprises benefit from preserved investments in custom logic and data models, coupled with tools that facilitate incremental enhancements rather than disruptive overhauls. PowerBuilder 2025 enhances modern relevance through features that integrate legacy architectures with cloud-native paradigms, including automatic generation of APIs, codeless UI theming, and support for n-tier cloud deployments, allowing organizations to modernize without accruing . These advancements enable scalable Web APIs and hybrid on-premise/cloud applications, appealing to businesses prioritizing stability alongside innovation.

Criticisms and Limitations

PowerBuilder has often been perceived as a legacy technology, particularly due to its steep for developers unfamiliar with its proprietary PowerScript language and , which contrasts with more contemporary tools like those in the .NET or ecosystems. This perception is compounded by its historical focus on client-server applications, with limited native support for mobile development until the release of PowerBuilder 2017, which introduced cross-platform mobile capabilities. A key limitation stems from its vendor dependency on the Appeon and ecosystem, as PowerBuilder's ownership by since 2010 ties users to specific runtime environments and updates controlled by these entities. Runtime licensing costs arise particularly with modern deployments via PowerServer, where subscriptions include limits on user sessions (e.g., a CloudPro plan supports up to 5 sessions), adding ongoing expenses beyond initial development licenses that start at around $1,595 annually. Performance issues have been noted with PowerBuilder's default P-code compilation, an interpreted format that can be slower than native in high-load or CPU-intensive scenarios, as P-code requires runtime interpretation while executes directly. However, these concerns have been mitigated in the 2025 release through an ultra-fast that achieves 2-3x faster builds. The PowerBuilder developer community remains relatively small compared to those of or .NET, with surveys indicating that most teams consist of 1-3 developers and more than 700 organizations employing larger groups of 15-300 specialists worldwide, with over 18,000 organizations using PowerBuilder in total. As of 2025, PowerBuilder receives a 4.0 out of 5 rating on based on user reviews. This smaller ecosystem results in fewer open-source resources, third-party libraries, and community-driven tools relative to more widely adopted platforms. Migration challenges are prominent when attempting to port PowerBuilder applications to modern architectures like , as the tool's monolithic design and tight integration with proprietary libraries make decomposition difficult without relying on vendor-specific solutions such as PowerServer for web-based redeployment.

References

  1. https://help.sap.com/docs/SUPPORT_CONTENT/sybpb/3362699176.html
  2. https://www.appeon.com/products/powerbuilder
  3. http://www.intertech.us/Portals/0/pdfs/Sybase_PowerBuilder.pdf
  4. https://www.nytimes.com/1994/11/15/business/sybase-to-acquire-powersoft.html
  5. https://www.latimes.com/archives/la-xpm-1994-11-15-fi-63027-story.html
  6. https://community.sap.com/t5/technology-blogs-by-sap/appeon-signs-agreement-with-sap-to-bring-major-innovations-to-powerbuilder/m-p/13213489
  7. https://www.appeon.com/company/news/appeon-signs-agreement-sap-bring-major-innovations-powerbuilder.html
  8. https://www.prnewswire.com/news-releases/appeon-signs-agreement-with-sap-to-bring-major-innovations-to-powerbuilder-300291905.html
  9. https://www.appeon.com/developers/powerbuilder-release-history.html
  10. https://hwvp.com/team/mitchell-kertzman.html
  11. http://displacedguy.com/the-powerbuilder-phenomenon
  12. https://community.sap.com/t5/technology-blogs-by-members/happy-25th-birthday-powerbuilder/bc-p/13223688
  13. https://www.nytimes.com/1993/04/04/business/profile-mitchell-e-kertzman-a-company-founder-who-bet-his-ranch.html
  14. http://chrispollach.blogspot.com/2018/03/pbhistory.html
  15. https://www.bloomberg.com/news/articles/1993-03-14/investors-hug-softwares-new-babies
  16. https://www.route-fifty.com/digital-government/1996/05/mastering-powerbuilder-50-is-tough-but-worth-the-effort/280381/
  17. https://www.cnet.com/tech/tech-industry/sybase-revamps-powerbuilder/
  18. https://www.eweek.com/development/sybase-to-ship-powerbuilder-9/
  19. https://www.prnewswire.com/news-releases/sybase-celebrates-20-year-powerbuilder-milestone-with-its-most-powerful-offering-129646188.html
  20. https://www.cnet.com/tech/tech-industry/sybase-fights-to-stay-in-tool-game/
  21. https://esj.com/articles/1998/09/23/sybase-wraps-up-enterprise-app-bundle.aspx
  22. https://www.romu.com/download/PB_vs_Java_wp.pdf
  23. https://evolveware.com/modernization-spotlight-future-proofing-powerbuilder-systems-that-provide-critical-citizen-services/
  24. https://community.sap.com/t5/additional-blogs-by-sap/a-deeper-look-at-sybase-powerbuilder-and-powerdesigner/m-p/12914877
  25. https://www.sap.com/investors/en/financial-news/ad-hoc-news/2010/05/934992.html
  26. https://www.datamation.com/applications/sap-acquires-sybase-for-5-8-billion/
  27. https://community.sap.com/t5/b-technology-blog-members/SAP%2BPowerBuilder/pd-p/67838200100800005660
  28. https://community.sap.com/t5/technology-q-a/when-is-powerbuilder-12-6-end-of-support-date/qaq-p/447011
  29. https://www.appeon.com/products/powerbuilder/migrating-to-pb
  30. https://www.appeon.com/products/whats-new/2025
  31. https://www.appeon.com/update
  32. https://docs.appeon.com/pb/whats_new/pb2025.html
  33. https://docs.appeon.com/pb2025/powerscript_reference/Language_Basics.html
  34. https://docs.appeon.com/pb2025/powerscript_reference/clicked_event.html
  35. https://docs.appeon.com/pb2025/powerscript_reference/open_event.html
  36. https://docs.appeon.com/pb2025/powerscript_reference/ch02s03.html
  37. https://docs.appeon.com/pb2025/powerscript_reference/xREF_87805_Standard_datatypes.html
  38. https://docs.appeon.com/pb2025/powerscript_reference/PowerScript_Statements.html
  39. https://docs.appeon.com/pb2025/powerscript_reference/xREF_57113_Using_SQL_in.html
  40. https://infocenter-archive.sybase.com/help/topic/com.sybase.infocenter.dc01261.1200/doc/pdf/PBNetFeaturesECL.pdf
  41. https://docs.appeon.com/ps2025/Enhanced_PowerScript_features.html
  42. https://docs.appeon.com/pb2019r3/application_techniques/ch02s01.html
  43. https://infocenter.sybase.com/help/topic/com.sybase.dc37812_0600/pdf/appeon_demo_applications_tutorial.pdf
  44. https://docs.appeon.com/pb2025/datawindow_programmers_guide/XREF_13867_Updating_the.html
  45. https://docs.appeon.com/pb2025/datawindow_programmers_guide/XREF_47050_Manipulating_data.html
  46. https://docs.appeon.com/pb2025/datawindow_reference/dwmeth_SaveDisplayedDataAs.html
  47. https://docs.appeon.com/pb/whats_new/DataWindow_enhancement.html
  48. https://docs.appeon.com/pb/whats_new/Supporting_high_DPI.html
  49. https://docs.appeon.com/pb2025/pbug/ug63671.html
  50. https://docs.appeon.com/pb2025/pbug/Working_with_Libraries.html
  51. https://docs.appeon.com/pb2022/pbug/Searching_targets_libraries_and_objects.html
  52. https://docs.appeon.com/pb2025/pbug/Defining_an_executable_application_project.html
  53. https://docs.appeon.com/pb2019/pbug/ch10s03.html
  54. https://docs.appeon.com/pb2019/pbug/ch13s02.html
  55. https://docs.appeon.com/pb2022/pbug/Working_with_Data_Pipelines.html
  56. https://docs.appeon.com/pb/whats_new/Modern_code_editor.html
  57. https://docs.appeon.com/pb2025/pbug/Using_Git_source_control_system.html
  58. https://docs.appeon.com/pb2025/installation_guide_for_pb/System_Requirements.html
  59. https://docs.appeon.com/pb2021/pbug/ug58941.html
  60. https://docs.appeon.com/pb2025/pbug/pbc_d_and_related_parameters.html
  61. https://stackoverflow.com/questions/2061590/full-build-incremental-build-and-deploy-within-powerbuilder
  62. https://docs.appeon.com/pb/whats_new/Using_new_compiler_or_old_compiler.html
  63. https://docs.appeon.com/ps2025/Automated_CI_CD.html
  64. https://docs.appeon.com/pb2025/getting_started/XREF_37915_Set_a_watch_and_a.html
  65. https://docs.appeon.com/pb2022/pbug/Debugging_an_application.html
  66. https://docs.appeon.com/pb2019/pbug/ch32s03.html
  67. https://docs.appeon.com/pb2025/pbug/Tracing_and_Profiling_Applications.html
  68. https://docs.appeon.com/pb2019/pbug/ch32s01.html
  69. https://docs.appeon.com/pb2022/application_techniques/Exception_handling_in_PowerBuilder.html
  70. https://docs.appeon.com/pb2022/objects_and_controls/RuntimeError_object.html
  71. https://docs.appeon.com/pb2025/pbug/ch04s01s03.html
  72. https://docs.appeon.com/pb2025/pbug/ug15079.html
  73. https://www.appeon.com/products/powerbuilder/ui-modernization
  74. https://docs.appeon.com/pb/whats_new/ch08s01s02.html
  75. https://docs.appeon.com/pb2025/pbug/Introduction_to_RibbonBar_items.html
  76. https://docs.appeon.com/pb2022/application_techniques/Creating.html
  77. https://docs.appeon.com/pb2025/pbug/ch04s02s11.html
  78. https://docs.appeon.com/pb2025/pbug/Specifying_the_UI_theme_for_the_application.html
  79. https://www.appeon.com/developers/library/videos/ui-themes.html
  80. https://docs.appeon.com/pb2021/application_techniques/Deploying_Applications_and_Components.html
  81. https://docs.appeon.com/pb2022/connecting_to_your_database/XREF_22487_About_the_ODBC.html
  82. https://infocenter-archive.sybase.com/help/topic/com.sybase.help.pb_10.5.connpb/pdf/connpb.pdf
  83. https://docs.appeon.com/pb2022/connection_reference/Encrypt.html
  84. https://docs.appeon.com/2017/server_configuration_guide_for_net/Application_security.html
  85. https://docs.appeon.com/ps2022r3/PowerServer_Deployment_Checklist.html
  86. https://www.appeon.com/developers/library/videos/powerbuilder-2019-release-webinar.html
  87. https://docs.appeon.com/ps2022/Build_and_deploy_the_PowerServer_project.html
  88. https://docs.appeon.com/ps2022r3/aws-deployment-architecture.html
  89. https://www.appeon.com/developers/library/videos/create-powerbuilder-application-runs-azure-using-powerserver-docker-containers-and-kubernetes.html
  90. https://docs.appeon.com/ps2025/whats_new.html
  91. https://www.appeon.com/products/powerserver
  92. https://docs.appeon.com/ps2022/Deploying_the_application_to_the_Kubernetes_cluster.html
  93. https://community.appeon.com/qna/q-a/does-appeon-do-progressive-web-apps-pwas-or-something-similar
  94. https://www.appeon.com/products/powerserver-licensing-faqs.html
  95. https://docs.appeon.com/ps2022/Import_license_and_activate_PowerServer.html
  96. https://docs.appeon.com/pb2021/connecting_to_your_database/ch01s01.html
  97. https://docs.appeon.com/pb2025/connecting_to_your_database/DB2.html
  98. https://docs.appeon.com/pb2025/connecting_to_your_database/PostgreSQL.html
  99. https://www.sqlines.com/powerbuilder/tutorial
  100. https://docs.appeon.com/pb2019/application_techniques/ch28s01.html
  101. https://docs.appeon.com/pb/whats_new/pb2017.html
  102. https://community.appeon.com/articles-blogs/tutorials-articles/2-powerbuilder/203-json-enhancements-in-powerbuilder-2017-r3
  103. https://docs.appeon.com/pb2019r3/application_techniques/ch04s03.html
  104. https://docs.appeon.com/pb/whats_new/Enhancements_to_calling_NET_assemblies.html
  105. https://docs.appeon.com/pb/whats_new/ch07s01s03.html
  106. https://docs.appeon.com/pb2021/native_interface_programmers_guide_and_reference/ch01s01.html
  107. https://docs.appeon.com/pb2025/application_techniques/ch04s08s01.html
  108. https://docs.appeon.com/pb/whats_new/ch09s09.html
  109. https://www.youtube.com/watch?v=uez_a1x0B0g
  110. https://community.sap.com/t5/technology-blogs-by-sap/developing-crystal-reports-applications-in-powerbuilder-net/ba-p/12912692
  111. https://www.appeon.com/developers/library/videos/net-assembly-importer.html
  112. https://docs.appeon.com/pb2025/pbug/ch01s01s01.html
  113. https://www.powerbuilder.eu/powerbuilder-blog/119-powerscript-why-is-it-immensely-powerful
  114. https://www.proexcellency.com/blogs/sap-online-training/what-job-roles-can-i-get-after-taking-sap-sybase-powerbuilder-online-training
  115. https://www.mphasis.com/home/thought-leadership/blog/healthcare-chronic-dilemma-to-modernize-or-maintain.html
  116. https://docs.appeon.com/ps2020/migration_guidelines/advantages_of_appeon_for_web_rad.html
  117. https://kumaran.com/powerbuilder-migration-java-vs-net-pros-cons/
  118. https://www.devx.com/enterprise-zone/42651/
  119. https://www.appeon.com/customers
  120. https://visualstudiomagazine.com/articles/2008/01/01/powerbuilder-revved-with-net-hooks.aspx
  121. https://community.appeon.com/qna/q-a/the-future-of-powerbuilder-and-what-could-be-done-about-it
  122. https://sync-sys.com/powerbuilder-to-cnet-modernization-for-nations-largest-natural-gas-distribution-utility/
  123. https://www.suntechnologies.com/case-study/re-engineering-of-automated-clearing-house-powerbuilder-application/
  124. https://www.suntechnologies.com/case-study/pb-to-java/
  125. https://community.sap.com/t5/technology-q-a/visual-studio-vs-powerbuilder/qaq-p/9521638
  126. https://www.prnewswire.com/news-releases/appeon-launches-powerbuilder-2017-with-cross-platform-mobile-development-capability-300482375.html
  127. https://www.appeon.com/pricing
  128. https://www.appeon.com/subscription/purchase-faqs.html
  129. https://community.appeon.com/qna/q-a/machine-code-in-64bit
  130. https://www.visual-expert.com/ES/visual-expert-blog/posts-2020/powerbuilder-survey-2019-research-report.html
  131. https://www.g2.com/products/powerbuilder/reviews
  132. https://www.optisolbusiness.com/insight/modernizing-powerbuilder-applications-in-banking
Add your contribution
Related Hubs
User Avatar
No comments yet.