However whatever anybody says in that sort of situation you're 'trying to prove a negative': running it in a situation for which it's not been designed, and while most of the time it might be OK you have absolutely no way of knowing whether you're about to hit something which will make it fall over.

I remember somebody saying that SQLite did have locking capabilities, and if that's the case then it /might/ be OK.

And- obviously- MS Access which is regularly maligned for its flakiness particularly when multiple users are involved. When I had to make a decision as to which server to use (a bit more than 20 years ago) there were very few choices unless you were prepared to slap a lot of money on the table and have IBM (or whoever) dictate to you what sort of hardware you had to be running.īefore that I had been involved in the sales/support of various database systems implemented as libraries (and sometimes, in the case of DOS, as TSRs) but all of them- without exception- were very wary of multiuser operation.īetween those points there were things like Borland Paradox, which tried to implement its own locking but would fairly regularly have problems.

Db browser for sqlite safe