Progress (OpenEdge ABL)

Progress (now formally OpenEdge Advanced Business Language, or ABL) is a strongly typed, English-like fourth-generation language (4GL) created for building data-intensive business applications. From its first commercial release in 1984, its defining characteristic has been the seamless fusion of a programming language with an integrated relational database, allowing developers to write database-driven applications with far less ceremony than the COBOL and C systems of its era required. Though rarely in the technology headlines, ABL quietly underpins thousands of enterprise resource planning (ERP) and line-of-business systems still running production workloads today.

History & Origins

Data Language Corporation (1981–1984)

Progress traces back to Data Language Corporation, founded in Bedford, Massachusetts in 1981 by Joseph Alsop — who would serve as the company’s longtime chief executive — together with co-founders Chip Ziering, Clyde Kessel, and Mary Szekely. The founders, reportedly veterans of the application-development market, set out to solve a recurring frustration: business applications of the time were typically written in COBOL on expensive IBM mainframes, or in C on departmental UNIX minicomputers, with the database treated as a separate and often awkward component.

Their answer was an architecture-independent language with a database built in. The language was designed beginning around 1981, and the first commercial version of the PROGRESS Application Development Environment shipped for UNIX in 1984, followed by an MS-DOS version in 1985. The pitch was compelling: write a business application once, in an approachable English-like syntax, and run it across the wildly heterogeneous hardware of the 1980s without rewriting it for each platform.

From PROGRESS to Progress Software

The product proved successful enough that the company renamed itself Progress Software Corporation in 1987, taking its identity from the flagship product. Progress went public on NASDAQ in 1991, and through the 1990s it expanded the language well beyond its character-terminal roots — Version 7 (1993) added graphical user interfaces and event-driven programming, and Version 8 (1995) extended client/server and cross-platform reach.

The OpenEdge Era

By the mid-2000s, the industry had developed a perception that 4GLs were less capable than general-purpose languages. In 2006, Progress responded on two fronts: it released OpenEdge 10.1A, which added a full object-oriented programming model — classes, inheritance, encapsulation, and strong typing — that could coexist with the existing procedural code, and it rebranded the language from PROGRESS 4GL to OpenEdge Advanced Business Language (ABL). The new name was a deliberate move to shed the 4GL stigma while keeping decades of existing applications running unchanged.

Design Philosophy

Progress was built around a few durable ideas that still distinguish it:

• The database is part of the language. ABL does not bolt a database driver onto a general-purpose language; data access is a first-class part of the syntax. A developer can iterate records, navigate relationships, and apply transactions using built-in language constructs rather than embedded SQL strings.
• Readability over terseness. Its English-like, verbose syntax — keywords such as FOR EACH, DISPLAY, and DEFINE VARIABLE — was a deliberate choice to make business logic approachable and self-documenting.
• Write once, run across platforms. Architecture independence was a founding goal, freeing applications from the specific hardware and operating systems of a fragmented market.
• Backward compatibility as a feature. Progress has long prioritized keeping older applications running, a quality that made it attractive for long-lived enterprise systems and explains the continued life of large ABL codebases.

Key Features

• Integrated relational database with transaction management, indexing, and a 4GL-native data-access model.
• English-like, strongly typed syntax that is also late-bound, balancing compile-time checks with runtime flexibility.
• Procedural and object-oriented models that interoperate, letting teams modernize incrementally rather than rewrite.
• Built-in UI and reporting facilities, historically for character terminals and later for graphical clients and the web.
• Modern integration: later releases added XML, JSON, REST, web services, and application-server capabilities, allowing ABL back ends to serve contemporary front ends.

1
2
3
4

/* A classic Progress / OpenEdge ABL data query */
FOR EACH Customer NO-LOCK WHERE Customer.Balance > 1000:
    DISPLAY Customer.Name Customer.Balance.
END.

Evolution

Progress evolved from a character-terminal 4GL into a full enterprise application platform:

The throughline is continuity: each generation layered modern capabilities on top of the existing model without forcing customers to abandon their investments.

Current Relevance

Progress OpenEdge remains an actively developed, commercially supported product, with OpenEdge 12.8 delivered as a long-term-support release in 2024. Its most visible footprint today is as the foundation of QAD’s manufacturing ERP, used by global manufacturers across automotive, food and beverage, life sciences, and consumer-products industries, along with a broad ecosystem of independent software vendors who ship commercial business applications written in ABL.

ABL is not a language that attracts newcomers browsing for the next trend; rather, it is a stable, vertically focused platform whose value lies in the enormous base of working enterprise software it supports. Progress Software, now a diversified enterprise-software company, continues to maintain and extend the platform for that installed base.

Why It Matters

Progress is a case study in a particular philosophy of software longevity. Where many languages chase generality and broad adoption, ABL bet on a narrow, well-defined problem — data-intensive business applications — and on never abandoning the customers who built on it. That bet produced a language that has stayed commercially relevant for more than four decades, quietly running ERP and operational systems that few outside their industries ever notice. For the history of programming, it stands as one of the more enduring examples of the 4GL movement: an attempt to let businesspeople and developers express data logic in near-natural language, paired with a database designed to make that logic effortless.