Thank you for your feedback and for the additional information.
Usually, the error you are experiencing occurs when the application tries to dispose the Database object twice. For example: when the Dispose()
method of the context is overridden, an instance of the context is enclosed in a using
statement, and then the Dispose() method is called explicitly.
To avoid the error, you could override the Dispose() method of the context but to remove the explicit call. That way, the instance of the context will take care to dispose the Database object on its disposal, at the end of the using
Regarding the workflow that would unlock the database file in your case, it seems like the scenario you are implementing has a lot of specifics, and currently, we do not offer a reliable out-of-the-box resource that demonstrates it. However, we are constantly gathering information and preparing resources based on the needs of our users, and I will make sure to update this thread once we are able to provide you with additional details.
In case you have further questions, do not hesitate to get back to us.
OpenAccess ORM Q3 2013 simplifies your model operations even further providing you with greater flexibility. Check out the list of new features
shipped with our latest release!