>I just had a DBC corruption yesterday just by adding a new relation (could not open it anymore, had to resort to an out-of-date backup) and you say that the whole weakness things about DBC/DBF is just a theory? You're just plain lucky if you never had a VFP table/database corruption.

C'mon Sylvain,

You had corruption on DBC container. DBC container is data dictionary
(data about data) so unless you are running some wild day to day development (structure changes) ANY previous copy will normally do.
Did you loose actual data ?

I saw this once but on someone else app. They had over hundred of tables with PR/RI triggers within single DBC. But If you keep data divided into moderate size DBC containers (as per some logical role in overal design) you will not see this happening a lot if ever.

I don't believe I am lucky. I foster literally hundreds of VFP databases
(MultiModule/Company/Year) at multiple site installations. And NEVER had such problem. But I never designed single database container holding more then 25 tables nor ever updated actual data records outside buffering/transaction band. This simply works.