>>Not what I would consider an elegant solution, I would much rather prefer that the >>business object took responsibility for which tables where to be saved

As Victor said, you could override stuff in the business object itself. If you want that behavior all the time, that would be ok. But if there were times when the business object shouldn't behave like that, overriding may not be the best.

Alternatively, you could create a method in your base buisness object named, for example, .RejectChanges(string tableName) and call it when you needed to.

Mike