>In my business rule layer I check to make sure the FK relationships are good before saving the item.
>Also in the case of deletes I would also check to make sure the item can be deleted before trying the delete. I would also present a user understandable error.

Yes, I had considered this tack as well. However, I just don't like having to make one or more calls to the database before making a call to the database. Seem likes wasted bandwith. It at LEAST doubles the traffic to the database.

>your business rule should present a user understandable error to the user.

Yes, this is exactally my goal. I am just hoping to do it by catching the exception and converting it to an understandable message.

BOb