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

Stability is a system/application behavior,
it is determined by the abilities of the developer,
data loss is a reliability behavior,
it is determined by the abilities of the designer.

You can use an application with 99% of stability , with 1% of data reliability
( the first example is VFP9 ).


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

SQL server cannot fix external malfunctions

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