>>A lot of commentary here about migrating from VFP to .NET, Python etc. I accept all the arguments (mainly anyway).
>>
>>Don't hear so much about which db to migrate to that fits the "crash safe" criteria I have for using VFP tables:
>>
>> * very difficult to harm the tables in power failures, random reboots, voltage spikes etc
>> * easy to strip out and rebuild table headers (and an app can sense and do this automatically)
>> * yet high performance ...
>>
>>My app is typically run on a laptop (or dodgy hardware) in a remote location. I have one on a mine site that I haven't been able to visit since 2001!
>>How robust is, say, MS SQL Server Compact Edition by comparison? Can you cut the power without corruption problems? Any other suggestions?
>
>Thanks to all who had suggestions. I'll evaluate these and more.

Why are you interested in stripping out and rebuilding table headers? Is that just to fix corrupted tables?

Not an ssue with SQL Server.