>Same here. BTW, that would make an excellent article!!!! :o)

Ah, so why don't you write it? <g> I'll probably get around to doing a blog about it soon, that'll be the extent of my writing. ;0)

~~Bonnie

>
>
>
>>>Coming from you that makes me feel much better! Thanks!
>>
>>You're welcome! There are other options as well, obviously.
>>
>>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.
>>
>>~~Bonnie