Short: writers killed 60 times each. Visual FoxPro and its OLE DB driver left a wrong index with no warning 51 times in 180. Thunder.Dbf never did, once.
Read the full write-up: Reading and writing dBASE and FoxPro files in modern .NET
More shorts from this video
Forrester: 1 in 5 B2B sellers would negotiate with buyers' AI agents in 2026 (0:19)
What ChatGPT's product feed requires: start with these 8 fields (0:29)
Why AI agent checkout is not ready for B2B buying yet (0:18)
ACP, UCP, AP2 or MCP: which agentic protocol should you pick? (0:13)
What is agentic commerce? The short definition (0:24)
Custom catalogs and tiered pricing in BigCommerce B2B Edition (0:46)
Do you need BigCommerce B2B Edition, or is standard enough? (0:46)
Getting ERP prices into BigCommerce B2B Edition (0:43)
BigCommerce B2B Edition buyer roles in 30 seconds (0:30)
4 things BigCommerce B2B Edition doesn't do (0:48)
What a BigCommerce ERP integration actually syncs (0:45)
Duplicate orders, stock and ERP outages in BigCommerce (0:42)
Every ERP has a catch: BigCommerce integration quirks (0:39)
How to pick a BigCommerce ERP connector: test three hard cases (0:40)
Why BigCommerce ERP connectors break on pricing (0:44)
Your business still runs on dBASE files. Now what? (0:30)
FoxPro indexes in 11 code pages, byte for byte (0:29)
50 hard power cuts while writing dBASE files (0:33)
49x faster DBF lookups than the VFP OLE DB driver (0:30)
Transcript
The harshest test for a shared file is a writer dying halfway through a change, the way a program does when someone closes a laptop lid. What matters isn't whether damage happens, since no file format can promise that. It's whether anyone finds out before the old program starts trusting a broken index. We killed each writer at a random moment, sixty times, and then let Visual FoxPro judge the table with its own tools. Visual FoxPro and its OLE DB driver left a wrong index with no warning fifty-one times in a hundred and eighty. Thunder.Dbf never did. Every time something was wrong, it said so, and refused to write until it was fixed.
Narration is an AI voice (Azure). The facts come from the linked write-up.