Visual DataFlex

Visual DataFlex is the Windows-era incarnation of DataFlex, one of the longest-lived database programming languages in commercial use. Launched in 1996 by Data Access Corporation of Miami, Florida, it took a fourth-generation language (4GL) that had been building business database applications since the early 1980s and rebuilt it around a visual, object-oriented development environment for Microsoft Windows. From version 4 in 1996 through version 17.1, the product carried the Visual DataFlex name; in 2014, with version 18.0, it was rebranded simply DataFlex — and under that name it is still actively developed today, with DataFlex 25.0 shipping in June 2025. Few proprietary languages have sustained a paying developer community across five decades of platform shifts, from CP/M terminals to the web and mobile browsers, and that longevity is Visual DataFlex’s defining story.

History & Origins

From hardware shop to language vendor

Data Access Corporation was founded in 1976 in Miami by brothers Chip and Cory Casanave. The company started out selling hardware, but the brothers pivoted to software, building up a library of database routines that gradually cohered into a full language. That language — DataFlex — was formally introduced at the COMDEX computer trade show in 1981, making it a relatively early example of a fully fledged, commercially used 4GL: a language in which a developer declares tables, indexes, and data-entry behavior at a high level and lets the runtime handle the mechanics.

The original DataFlex’s signature trick arrived with version 2.3 in 1987: genuine portability. The same application code could run across CP/M, MS-DOS, TurboDOS, Unix, and other architectures of the day — highly unusual for the era, and a major draw for vertical-market software houses that needed to sell into whatever hardware their customers happened to own. By the mid-1980s DataFlex applications were running everything from automated inventory control to insurance fraud detection, and by the early 1990s — when DataFlex 3.0 modernized the product and pushed it toward object orientation — roughly ten thousand companies were reported to be using it.

Going visual

The rise of Windows in the early 1990s posed an existential question for every character-mode development tool. Data Access answered in 1996 with Visual DataFlex, released as version 4 to signal continuity with the existing DataFlex line. It paired the DataFlex language with a visual integrated development environment in the mold of Visual Basic, Borland Delphi, and Visual C++: developers designed forms visually, wired them to database tables, and extended behavior by subclassing a rich object-oriented framework rather than writing plumbing from scratch.

Data Access moved early on the web, too. In 1998 it launched its WebApp Server, which let DataFlex developers serve their database applications as HTML web applications — an ambitious offering at a time when dynamic database-backed websites were still a specialist discipline.

Design Philosophy

Visual DataFlex was designed around one job: building data-centric business applications with as little incidental code as possible. Several principles follow from that:

• The framework is the application. A Visual DataFlex program is largely a tree of objects — views, data dictionaries, database objects, controls — instantiated from framework classes and customized by setting properties and overriding messages. Standard behavior (find, save, delete, validate) comes for free.
• Data Dictionaries as a business-rules layer. DataFlex’s data dictionary classes centralize validation, defaults, relationships, and referential behavior in one place, so every form or web view that touches a table automatically enforces the same rules. This separation of business logic from user interface was a distinctive strength long before it became mainstream practice.
• Database independence. Applications are written against a logical data-access layer, with drivers connecting to the embedded ISAM database or to SQL back-ends such as Microsoft SQL Server, IBM Db2, MySQL, and ODBC-compliant systems — echoing the hardware portability that defined the original DataFlex.
• Pragmatic typing. The language is loosely typed, with the runtime managing conversions between strings, numbers, and dates. That fits the 4GL ethos: the developer describes intent, the runtime handles representation.
• Evolution without rewrites. Data Access has consistently prioritized carrying existing applications forward — from DOS to Windows, Windows to web, 32-bit to 64-bit, ANSI to Unicode — so that decades-old vertical applications can keep pace with modern platforms.

Key Features

• Object-oriented language with classes, inheritance, and a message-based model (Send, Get, Set) layered over an imperative core that still shows its 4GL ancestry.
• Visual Studio-style IDE (the DataFlex Studio) with visual designers for Windows forms and web views, code sense, and integrated debugging.
• Data Dictionary framework encapsulating validation and relational integrity independent of any particular user interface.
• Windows and Web frameworks from one language: the same skills and much of the same business logic serve desktop applications, browser-based web applications, and mobile-styled web front ends.
• Broad database connectivity, from the embedded DataFlex database to Microsoft SQL Server, IBM Db2, MySQL, and other back-ends reachable through ODBC.
• Web services support for both publishing and consuming services, letting DataFlex systems participate in modern integration architectures.

A flavor of the language’s message-based style:

Object oCustomerView is a dbView
    Set Label to "Customer Maintenance"

    Object oCustomer_DD is a Customer_DataDictionary
    End_Object

    Set Main_DD to oCustomer_DD
    Set Server  to oCustomer_DD

    Object oName is a dbForm
        Entry_Item Customer.Name
        Set Label to "Name:"
        Set Size to 13 100
    End_Object
End_Object

Evolution

The product’s history falls into three eras. The character-mode era (1981–mid-1990s) established DataFlex as a portable 4GL for business databases. The Visual DataFlex era (1996–2014, versions 4 through 17.1) rebuilt it for Windows: object-oriented framework, visual IDE, SQL back-end drivers, and — starting with the WebApp Server in 1998 and culminating in the DataFlex Web Framework introduced with version 17.1 — a serious push into browser-based applications. The modern DataFlex era (2014–present) began when version 18.0 dropped “Visual” from the name, reflecting a product that had become as much about the web as about Windows.

Recent releases show the platform still moving: DataFlex 2021 (20.0) was a landmark, delivering 64-bit application support and full Unicode along with re-engineered SQL drivers; DataFlex 2023 (23.0) added FlexTron, blending DataFlex web components into Windows desktop applications; and DataFlex 25.0 arrived in June 2025. Data Access Worldwide, headquartered in Miami, develops the platform today with offices in Hengelo in the Netherlands (Data Access Europe) and São Paulo, Brazil.

Current Relevance

Visual DataFlex — under its modern DataFlex name — remains a commercial, actively maintained platform with annual releases, a dedicated developer community centered on Data Access’s forums and the dataflex.dev hub, and an installed base concentrated in vertical business software: construction estimating, healthcare, housing management, leasing, ERP, and countless line-of-business systems built by independent software vendors since the 1980s. It is a niche by any mainstream measure — you will not find DataFlex near the top of language popularity indexes — but it is a durable niche, because the applications built on it encode decades of domain knowledge and the platform keeps giving them a path forward: to SQL back-ends, to the web, to 64-bit and Unicode, without ground-up rewrites.

Why It Matters

Visual DataFlex matters as a case study in software longevity. It demonstrated, earlier than most, ideas that became industry orthodoxy: write-once portability across operating systems in the 1980s, a centralized business-rules layer separated from the user interface, and a managed migration path that let the same codebase travel from terminals to Windows to the browser. It also represents a whole stratum of computing that popularity rankings miss — the proprietary 4GLs (alongside Clarion, 4D, and PowerBuilder) on which a generation of vertical-market software companies built their products. Nearly fifty years after Data Access was founded and thirty years after Visual DataFlex brought the language to Windows, the platform’s continued evolution is a reminder that in business software, the ability to preserve and modernize working systems can matter more than fashion.