There is no way to guarantee that corruption won't happen.
Application architecture has a big effect on corrupt index files. Don't every directly access fields in the DBF. Always use buffering. Add the FLUSH command after every save. Those things will help.
>It's an age old question, but how can we prevent indexes of native VFP DBF's from "corrupting"? we have already deployed daily "reindex" tools, but almost everyday corruption happens...
>
>Assuming we cannot resolve network (hardware) concerns, is there no other way to safeguard indexes from network interruption or other external factors that tend to cut connection to dbf server?
>
>Really need a solution for these, we have tried recoding our applications but to no avail.
>
>Thanks.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer