Re: Tasty exceptions

I should have mentioned that this is an in-house app with about 30 users.
The clue came when I was done with a PCAnywhere session on the db server and
accidentally clicked the novell 'Log Off' (or something like that) button
instead of 'Lock Workstation' which shut down the database. I cleverly
correlated that action with the people calling and cussing, and was able to
easily duplicate the problem by pulling out my network cable while
debugging. :)

Actually, I upgraded from Oracle 8i to 10g on Sunday, and think I read
somewhere that odac has the capability to automatically try to restore a
lost connection on 9i or greater.. So I can hopefully get rid of that code
when time permits.

"Wayne Niddery [TeamB]" <wniddery@xxxxxxxxxxxxxx> wrote in message
news:44a2a989@xxxxxxxxxxxxxxxxxxxxxxxxx

So then how do you figure out that this is what is happening? At the very
least you should be logging the exception somewhere so it can be
discovered. *Eating* it implies simply suppressing the exception and
attempting to carry on as though nothing is wrong.


.