>Moving to C/S does not prevent corruption and if a SQL Server record is physically corrupt you may see lockups merely trying to access it. But they are much less common. A properly maintained C/S database can deliver effectively permanent reliability/availability for years.

Amen. All of the data I store in any of the systems I design or work with now is in SQL Server because of the rock solid reliability of the data store. Make sure the server itself is solid and up-to-date and you will rerely if ever have data corruption (at least not at the server or database level - a user can still store garbage if their program and the database allows).

It took several months to really get into using SQL Server data instead of VFP tables, but once I got the hang of it I never look back!

BTW my primary client stores medical data for millions of people gathered over the last 20 years from multiple earlier companies. Primary database size is approx 100GIG. We have had no corruption in the almost 2 years we have been using SQL server as the data store (previously stored on a mainframe and various other database systems).