Originally posted by gandolf989
If the MS OLE DB Driver for Oracle was coded correctly, what should be the outcome for your test?

Should you get a message saying that the database is no longer available?

It seems that you are upset because you don't like the error hadling for a Microsoft supplied program. Try plugging the cable back and see if it works.

If it does add to the documentation that the network cable must be plugged in.
The problem is, there is no error handling in their code for this condition. The app crashes inside their DLL. I am not returned an error, because it never gets to that point. When I go to the call stack in VS .NET 2003, it doesn't show anything from my program in the stack. It's all in kernel32.dll and the driver if I remember correctly. I could post the call stack in case anyone would like to see it, but I doubt that would help identify what exactly is going on. My guess is, it's a bug in the MS OLE DB for Oracle driver.