>>> [KG] What I called into question is the quality of the product.
....
>>For me it is a solidly working bee doing it's stuff extremly well - can you point me to many reports of data loss using SQLite stemming from internal programming errors ? It is not MEANT to be MU-ACID.
>>
>
>To me, it depends on the requirements of the app. If it shares backend access with other apps with high traffic then there may be issues:
>
>http://www.sqlite.org/whentouse.html
>
Total ACK from my side - I was referring in my other post to the equivalent of a header lock in vfp terms for writing as "weakness" and the inadvisability of file ISAM for MU brought on by technical "advances" like SMB2 as the other point mentioned in some OS' having basic errors [the linux samba locking errors of around early this century are gone AFAIK, but have not checked in detail].

Quality without further definition/qualification is IMHO nearly useless as a category.
Even low cost cars are sometimes perceived as "good quality" when they break down more often than higher priced ones because the price ratio is better: the customer got "enough for the money".

It is somewhat unbelievable that Nokia, Apple, all android makers are basing their HW on software KG knows to be "of dubious quality" to twist the words a bit more than he actually wrote ;-)

regards

thomas