If you open a database in DB4S that is also open in another process, then if you make changes to the database and click "Write Changes", the changes are not written to the database. The journal file goes away and the changes remain in DB4S in memory, but as soon as the database is closed and reopened, the changes are gone. There is no warning or error displayed.
Thanks for reporting it. Yeah, we should at least detect that the changes aren't written, and warn the user when it happens.
@Kudalufi This seems solved long time ago. I always get "database is locked" errors. Would mind confirming it with our current alpha version for the next release?
I'll close this, as this appears resolved in our latest builds.

@Kudalufi - I appreciate its been a while since you opened this issue, but if you still use DB4S, I'd recommend you using the latest nightly/beta and trying again.
Most helpful comment
I'll close this, as this appears resolved in our latest builds.
@Kudalufi - I appreciate its been a while since you opened this issue, but if you still use DB4S, I'd recommend you using the latest nightly/beta and trying again.