Chaim,
This is one of the biggest criticisms of file-based storage: the intermittent unpredictable glitch. The traditional response is to convert to a C/S database that will bring reliability benefits as well as improved security and scaling. It doesn't have to cost a fortune: take a look at mySQL which is an open source C/S Database. We just installed it on a box and pointed VFP RVs at it with no problems (though some of the field types needed tinkering.) If you use VFP views you could easily offer MySQL as an upsizing value-add option. If you distribute MySQL with your commercial product you'll run into licensing costs, but if it is an optional extra you should not experience any price penalty. Alternatively if your customers can afford SQL Server or Oracle you could roll that into an ever bigger value-add and charge a fortune. ;-)
IMHO you *definitely* should raise this with the decisionmakers ASAP. If you don't, somebody else will and they'll have wide support. Iin the past this has resulted in loss of business for some posters here who tried to stick with file storage for the benefit of the customer/s but were outpositioned and outsold by players that picked holes in all the weaknesses of file storage and converted it into a "these guys are putting your business at risk, let us come in and safeguard your data" scenario.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1