Bonnie,

>>That's typically something I'll check before I ever send the updates to the backend so that the user can fix it. Unless you're not talking about user-input values.

Yes these are user input values. And yes I'm trying to check for uniqueness before I send the user updates. The only way to do that however is to run a SELECT statement against the database to see if the values already exist before sending the updates. I'm just not sure how to do that in the context of the framework.

In MM.NET there is a specific hook which calls an overridable function. This is where such checks are supposed to be coded. Unfortunately by the time the CheckRulesHook() method is called the transaction has apparently already begun.

Max...