The exception that you are experiencing usually is related to concurrency issues when one client modifies the data and commits a transaction that affects another client manipulating the same data. It can happen even if you have no multiple threads in your application, but just by starting the client application twice (or more).
I would like to ask you if you can check whether the record that you are trying to delete is in the database before and after you have performed the delete operation. If you find the record in the database after the delete has thrown this exception please send us your code with more detailed description of the scenario so we can analyze it for any issues in our side.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map