dBase died from litigation, vendor lock-in, and neglect; AI-powered migration tools now offer an escape route for trapped legacy codebases.
Key Takeaways
Ashton-Tate CEO Ed Esber chose lawsuits over innovation, targeting customers with piracy audits and poisoning developer trust.
Competitors FoxPro and Btrieve shipped UNIX and Novell-compatible servers while dBase stalled; market share collapsed.
BDE runtime files timestamped 1998 shipped in dBase 12+; meaningful development stopped after 2019.
Third-party vendors shipped binaries without source, sold fake subscriptions, hid behind shell LLCs, then retired and vanished.
Frontier AI models (Claude, ChatGPT) can now parse .PRG, .NTX files and translate 16-bit dBase/Clipper/FoxPro to Rust, Go, or Dart.
Hacker News Comment Review
Commenters note Microsoft Access 2.0 already provided a practical DBF migration path via import/export filters in the WFW 3.11 era, predating AI tooling by decades.
Consensus frames the dBase arc as a textbook case: litigation and complacency as a compounding death spiral, not a single failure point.
Notable Comments
@orionblastar: notes Turbo C and Pascal DBF readers existed but “hardly anyone used them” – most legacy data survived in plain text files.
