>I probably should have mentioned this in my first reply, but the main downside to this solution is that all your calls to these methods >need to remember to check the oException property ... so all your developers need to be aware of this or it could cause problems.
>
>Our Framework initially worked this way (in fact, I've frequently posted some code for a DataAccess base class that does this, or >something similar), but as we hired more and more developers, we wanted something a little more fool-proof; so we ended up >refactoring to utilize anonymous delegates. I don't have any sample of that methodology thrown together at this time, but perhaps I >should do that some day.

I have thought of this issue too. I'd like to see your example if/when you can post it.