>>So, it seems to me that VFP file tables are really hard to maintain. We keep on reindexing files at least 3 times a month. The system that I am currently handling is a hospital system which has volumenous records at least 4,000 invoices a day. Our client is getting angry why they need to do such thing? Is SQL Server a silver bullet solution for this?
>
>It depends :)
>
>Back in Yugoslavia I had to write crashed table rebuilder, and a foolproof automatic indexing routine, which would close everything, kill indexes, write new ones from scratch, and restart the app if there was one of typical errors on table opening - because we had lousy hardware, various ways of breaking network cables, and power outages. Here, I had to rebuild the same table twice, both times for the same customer, on the same workstation, because the network cable was switched from one machine to another, and probably got loose in the process. But that is all I had here. Most of the machines have UPSes (even workstations), electricity is stable, and you don't get the house electrician to lay down the network cables (well, most of the time).
>
>So even if SQL Server may be the silver bullet, it may occur that the quality of the silver is not enough. It may suffer from various physical circumstances as well, who knows. Don't know your environment, though, so this sort of experience may not apply.

I agree. The only time my tables have been corrupt is when I did something foolish. The hospital network is stable, the users are well-trained not to turn the machine off unless tech support has tried everything else. No curruption. No maintenance on my part.