Videos

Kill a FoxPro write mid-change: who leaves a silent bad index?

0:41 · November 18, 2026 · Watch on YouTube

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

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.