I agree with Thomas. Get Stonefield. Additionally, there are two main reasons I've found for data corruption: 1) Stupid Programmers 2) Stupid Users.

Stupid programmers are developers that don't do the right stuff in their programs to eliminate these problems. Somethings that can be done are use views, buffering, FLUSH, etc.

Stupid users are people that simply power off or reboot, don't backup etc.

Once you have determined you are not in the stupid programmer group, then educate your users. After that, do what I do ... charge them triple rates to fix corruption problems. They only have to pay that once or twice before they start to learn.


>Most of my clients are small business types. Of course I use VFP almost exclusively to design and write their apps. But one thing that keeps bugging me is when will it be my turn to fix a corrupt table and the all the grief that come with it. Fortunately, that day has not come yet, but I feel it will soon.
>
>There is no way that I'll convience one of my "MOM-POP" shops to fork out some bucks to purchase a client server like MS SQLServer or Oracle.
>
>My question is is there a better tables/database that is "more" stable and "reliable" then the VFP native tables?