VDF

VDF is the abbreviation the developer community uses for Visual DataFlex, the Windows-based visual incarnation of DataFlex — an object-oriented, fourth-generation language for building database business applications, created by Data Access Corporation of Miami, Florida. Launched in 1996 as the graphical successor to the character-mode DataFlex that had shipped since the early 1980s, Visual DataFlex carried the product name (and the VDF moniker) until 2014, when Data Access dropped the “Visual” and reunited the platform under the original DataFlex brand. Under either name it is the same continuously developed language: a commercial 4GL whose specialty is turning database schemas and business rules into working Windows, web, and mobile applications quickly, and which remains in active development today — DataFlex 2025 (25.0) shipped in 2025.

History and Origins

Data Access Corporation was founded in June 1976 in Miami, Florida. Its flagship product, DataFlex, was presented at the COMDEX trade show in 1981 and released commercially in 1982 — one of the early commercial fourth-generation languages, designed so that a developer could describe data structures and business operations at a high level rather than hand-coding file handling in a 3GL. Portability was the young product’s calling card: DataFlex applications ran across an unusually wide spread of systems, including CP/M, MS-DOS, TurboDOS, Novell NetWare, OS/2, Unix, VMS and IBM AIX, and the 2.3 release of 1987 made running the same application code on almost any supported architecture a headline feature. During the 1980s DataFlex applications handled workloads such as automated inventory control and insurance fraud detection.

DataFlex 3.0 arrived in 1991 with a modernized interface, and over the early 1990s the language took on object orientation, with roughly ten thousand companies using the product line. The decisive turn came in 1996, when Data Access launched Visual DataFlex: a Windows-based visual development environment in which applications were composed from object hierarchies — panels, views, data-entry objects — bound to the database through the language’s data dictionaries. Its version numbering began at 4, picking up where character-mode DataFlex 3.x left off. The DataFlex WebApp Server followed in 1998, hosting the same business logic behind web front ends.

Design Philosophy

Visual DataFlex is unapologetically a tool for database business applications, and its design decisions all serve that goal:

• Data dictionaries as the heart of the application. Business rules — validations, relationships, defaults, constraints — live in Data Dictionary objects (DDOs) shared by every view, report, and web service that touches a table, rather than being scattered through UI code. Change the rule once and every part of the application obeys it.
• Database independence. Applications are written against the DataFlex data-access layer, with drivers for the embedded DataFlex database as well as Microsoft SQL Server, IBM Db2 and ODBC back-ends — the ODBC route reaching databases such as MySQL and PostgreSQL — so a system can switch databases without rewriting application code.
• Declarative object composition. Programs read as nested Object ... is a Class ... End_Object blocks whose properties are Set at definition time — closer to describing an application than scripting one, with event procedures filling in behavior.
• 4GL pragmatism over type ceremony. Typing is loose; the runtime converts between types as needed, keeping the language approachable for the business developers it targets.
• Protect the investment. Data Access has repeatedly moved the platform to new technology generations — DOS to Windows, Windows to web and mobile — while keeping decades-old application logic migratable, a continuity few commercial tools have sustained.

Key Features

A minimal Visual DataFlex-style Windows program shows the declarative object idiom:

Use Windows.pkg

Object oMain is a Panel
    Set Label to "Hello from VDF"
    Set Size to 100 200

    Object oGreetButton is a Button
        Set Location to 40 70
        Set Label to "Greet"

        Procedure OnClick
            Send Info_Box "Hello, World!"
        End_Procedure
    End_Object
End_Object

Start_UI

Notable capabilities of the platform include:

• An integrated Studio with visual designers for Windows forms, web views, and reports, wrapped around the language, compiler, and debugger
• Data Dictionary objects that centralize validation, relationships, and business logic per table
• The DataFlex Web Framework (introduced with Visual DataFlex 2012/17.1, released in 2013) for browser-based and mobile-touch applications served by the WebApp Server on Microsoft IIS
• Web services support, publishing and consuming SOAP and JSON services from the same business logic that drives desktop views
• FlexTron (DataFlex 2023), which lets web-framework controls run inside Windows desktop applications, blending the two UI worlds
• Bytecode compilation: programs compile to bytecode executed by the DataFlex runtime, the mechanism behind the product line’s historical cross-platform portability — though the language notably lacks built-in threading

Evolution

The through-line of VDF’s history is reinvention without rupture. Character-mode DataFlex (1982) became Visual DataFlex (1996) for the Windows GUI era; the WebApp Server (1998) and later the Web Framework (2013) carried the same language onto the web; and in 2014 the “Visual” prefix — by then describing only one of several deployment targets — was retired with the DataFlex 2014 (18.0) release. Modern releases adopted year-based branding: DataFlex 2021 (20.0) was a watershed, re-founding the platform on full Unicode and 64-bit architecture with re-engineered SQL drivers; DataFlex 2023 (23.0) added FlexTron; and DataFlex 2025 (25.0), released in 2025, is the current version. The flagship development environment, once spread across many operating systems, is today Windows-only, while applications reach browsers and mobile devices through the web framework.

Current Relevance

DataFlex remains a living commercial product from Data Access Worldwide, with offices in Miami, Hengelo (Netherlands), and São Paulo, and a user community concentrated in North America, Europe, and Brazil. The ecosystem is small compared with mainstream languages but notably loyal: annual gatherings such as the European DataFlex Users’ Conference (EDUC), third-party specialists like Unicorn InterGlobal, and independent software vendors who have shipped DataFlex products for decades. Its center of gravity is vertical line-of-business software — notary practice management, billing systems, logistics, and other data-intensive niches — where the original 4GL promise of fast development against a reliable database still pays rent, and where systems begun in the character-mode era have been carried forward, migration by migration, into web and mobile deployment.

Why It Matters

VDF is one of the great survivors of the fourth-generation-language movement. Most of the 4GLs that flourished alongside DataFlex in the 1980s are gone or frozen; Visual DataFlex navigated the DOS-to-Windows transition in 1996, the web transition starting in 1998, and the Unicode/64-bit transition in 2021, keeping a single language and its applications viable across more than four decades. Its data-dictionary architecture — business rules defined once, enforced everywhere — anticipated concerns that mainstream frameworks later addressed with ORM validation layers, and its database-independence promise predates today’s abstraction layers by decades. For anyone studying how programming platforms age, VDF is a case study in the road not usually taken: rather than dying with its original platform, a proprietary language repeatedly rebuilt its delivery mechanism while preserving its users’ code — and is still shipping releases in 2025.