>>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?
>
>I have never experienced a currupt VFP table. In DOS xBase, sometimes, usually due to a logic problem in MY program. But have not seen a broken one since VFP 6. Even when a really cold reset is called for. Many times I suspected bug outs
>in my projects were a VFP bug. And, always, it turned to be my quality assurance vacations:-)

Terry;

You are indeed lucky. We had a major client who had a problem due to bad data. The owner of our company was away and we received a call from the president of the client company - very upset – with the threat of law suit, etc. I was the lead programmer and sent one of our guys with a zip drive to the customer site, 120 miles away. Back came the data but I could not open the table. This table had 80 million records and had all shipping data for the company. With FoxFix I repaired the table and did some calling to the client. Seems one of his men in the warehouse turned off the server right in the middle of the busiest part of the day.

Trying to do something proactive got me in trouble with the owner. When he returned I told him what happened and he got mad at me for helping. He told me to call the president back and tell him next time it will cost you $1200 to fix the problem. And here we thought we were doing a good job! These guys even had a service contract with us. Oh well, you can’t win!

Tom