>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!


Means nothing else but poor design of that particular application.

I am using bufferring/transactions on vfp native dbcs/tables for decade
now without single corruption! If you open every table in buffered mode
then they are sort of 'detached' from hard disc. If everything is buffered
(5 - optimistic) and you have framework equiped to do central saving
alwas in some distinct miliseconds uppon user pressing his save button then
corruption is very unlikely to occur.
(This solution is suggested/explained in VFP Dev manual for VFP5!)

IMO Corruption on VFP tables is a myth comming from 'troubled chilldhood' of early foxpro applications. With VFP5 and onward; When developer is grown up, then he can *parent* quiet happy chilldren (robust apps) with VFP databases only ;)

What command using enterprise level database as backend, is only data volumes
that VFP cannot sustain by it's design, having in mind 2gb per table limit.
Other than that, I don't see any other reason.

Sergio