Is DataFlex end of life? Every version, every date, every risk
DataFlex is not end of life as a product: Data Access Worldwide shipped DataFlex 2025 in April 2025. But the versions most UK businesses actually run are long out of development. DOS-era character-mode DataFlex cannot run natively on 64-bit Windows, the Visual DataFlex name was retired when DataFlex 18.0 shipped in 2014, and the pool of UK DataFlex developers is vanishingly small. The deadline that matters is not a vendor date; it is the day your developer stops answering the phone.
“Is DataFlex end of life?” is the wrong question, and the people asking it deserve a straight answer anyway. Here is the precise picture as of June 2026, version by version, with the dates that matter.
The answer in one paragraph
DataFlex the product is alive. Data Access Worldwide, the Miami firm whose language this has been since the early 1980s, announced DataFlex 2025 (version 25.0) on 9 April 2025 and continues to sell and develop it. DataFlex the system in your back office is another matter. If your screens are green on black, you are on character mode, whose DOS-era runtimes no 64-bit Windows can run natively. If your system says Visual DataFlex anywhere, you are on a name that was retired when DataFlex 18.0 shipped in 2014. Either way, the clock that matters is not on a vendor website. It is the availability of people who can safely change your system, and in the UK that number is vanishingly small.
Every era, every date
| Era | Versions | Years | Where that leaves you in 2026 |
|---|---|---|---|
| Character mode (DOS and Unix) | DataFlex 2.x to 3.2 | Early 1980s to the late 1990s | Out of development for decades. The DOS runtimes are 16-bit and cannot run natively on any 64-bit Windows; the late 32-bit console runtime runs, but nothing about it is current |
| Visual DataFlex | 4 through 17.1 | 1996 to 2014 | Superseded. VDF 17 shipped in 2012; the Visual DataFlex name was retired when DataFlex 18.0 shipped in 2014 |
| Modern DataFlex | 18.0 (2014) through 25.0 (2025) | 2014 to today | Actively developed and sold by Data Access Worldwide |
Three useful facts fall out of that table.
First, if your system started life on green screens, it predates the entire Visual era. The data formats are proprietary .DAT files designed for machines with less memory than a modern smart bulb, and they have outlived every machine they were designed for. Built well, clearly. Still a liability.
Second, the gap between “your version” and “the current product” is now measured in decades, not releases. A VDF 17 system, the newest most legacy estates get, shipped in 2012. Everything Data Access has built since has moved the platform away from what your system is written in.
Third, the vendor is not coming to move you off. Their business, quite reasonably, is keeping you on DataFlex. The upgrade path they offer leads to DataFlex 2025, not to an open stack. If you want out, that is a different trade, and it is the one we do.
What “end of life” actually means here
Microsoft platforms die with a press release and a lifecycle page. DataFlex systems die differently: one retirement at a time.
The risk is not that DataFlex stops existing. It is that your version stopped being developed years ago, the developer who knew your system has retired or is about to, and recruiting a replacement is close to impossible. Try advertising for a UK DataFlex developer and see what comes back. That scarcity, not any vendor date, is the deadline.
There are sharper edges too. Character-mode systems need 16-bit support that 64-bit Windows simply does not have, which is why so many of them live on one elderly PC that must never be turned off. And UK Cyber Essentials requires unsupported software to be removed or isolated from the internet, which puts an unsupported runtime squarely in the auditor’s sights.
What to do about it, calmly
The wrong move is panic. A DataFlex system that has run for decades will usually keep running this quarter; the point is to stop betting the business on that sentence staying true.
The sensible sequence: secure the installers, source code and passwords; take an image of any machine the system uniquely depends on; test a restore from your backups; then get an honest map of your options. We compare staying, refactoring, replacing and rewriting honestly on the DataFlex migration page, and the same comparison for your specific system is what a free Legacy Risk Audit produces: a 30 minute call and a one-page written risk summary.
The full working method, from .DAT extraction to cutover, is written up in the DataFlex to PHP and MySQL migration guide, and further war stories land here in Field Notes as the work allows.