Hello Ludovic Ferrandis, thanks, but this is not quite true for the latest version:
http://www.sqlite.org/faq.html#q8 reads: "The restriction on moving database connections across threads was relaxed somewhat in version 3.3.1. With that and subsequent versions, it is safe to move a connection handle across threads as long as the connection is not holding any fcntl() locks. You can safely assume that no locks are being held if no transaction is pending and all statements have been finalized." Opening a DB in one thread and closing it in another works fine without SQLITE_ENABLE_MEMORY_MANAGEMENT, so I assume that this is causing me trouble. Especially, since SQLite causes an AV which crashes the application instead of issuing an error message or just silently do nothing about the shared memory. Ralf >You have to call open & close in the same thread, and in each thread if >needed.
