>To fix the problem I have to look for corrupted records and delete them, check for effects on relational data, and re-index the table. This is not fun work and the time is not billed. We're currently working on a utility to automate the fix. However, I was wondering if there was something I could do to make VFP tables "more stable".
>
I don't have enough time in with vfp yet for guarantees (most of my customers still have my fpd 26 app) but, so far, I can say that I have had no data corruption problems at all with vfp. The primary difference, I think, is that I use views for all data access. I remember several years ago here on UT someone else saying that and it was one of the factors that I considered when redesigning my application.