>Data curruption ( already saved on HDD ) should not happen. 'Data loss' of current entry is not a big issue.
>
>We are still using FPD 2.6, it VFP better ( with .dbf backend )?

The difference between 2.6 and 9.1 is enormous, what else did you expect? Look at the calendar, it's 2006. Upgrade NOW! Comparing 2.6 to 9.1 is like comparing a bicycle to a Ferrari; they both have wheels, everything else is different.

>Rakesh
>
>>except for a HD failure and software bugs, SQL SERVER don't lose data
>>
>>Yes, I've used SQL Server for over a decade and have been highly inpressed with its stability.
>>
>>But I've also seen data loss on flaky networks with PC freezes. If there are issues on the PC or between the PC and the server, converting to SQL Server will not fix those. A data entry clerk can carefully enter a scrreen of complex data, then the #$^$^%$$^ PC freezes again and the work is lost. You need to fix whatever is causing the freezes.
>>
>>This isn't an argument against SQL Server. It is an argument for investigating the cause of the freezing, not just changing database which seemed to be the proposed solution at the start of the thread.