Well, I'd have to agree with Craig and Thomas. I rarely have corrupted data. Very rarely. And then only one record. But I'm not opposed to a SQL Server/Oracle/MySQL/whatever backend. It's just that not everyone wants to or has the skills to maintain those systems, so it just depends on the situation.


>My experience is that almost all of the corruption and pack issues with DBFs can be eliminated with a good application architecture.
>
>>In the 5 years we have been dealing with RMS, support required for MSDE or SQL Express has been almost nonexistent. It is as plug and play as you get.
>>
>>Actually, in the decade I've been using SQL Server/Express/MSDE for my systems (single desktop to large enterprise) and converting systems over from fox tables to SQL backends, the only comments we get are about how nice it is to have stable, reliable data with the SQL backend.
>>
>>I've gotten stuck just recently maintaining a large VFP based system that runs on fox tables for the State of Kansas - what a pain in the a$$! Think it's time to pack and reindex? Who has that record or table locked? Uh oh, power flicker - corruption time!
>>
>>My contract is for me to migrate this to .NET and SQL server, but it is in such a sorry state right now that we are just trying to band-aid it enough to keep running while we work on the new system.