(sorry for the double post in two news groups. Forgot to add this one by
accident)
Here's the problem that I'm having.
Our application in debug mode doesn't link in Application.ThreadException,
it only functions when in debug mode. (did this with a compile directive) so
that we get errors on the right error line etc. Makes everything easier for
debugging in debug mode. However in release mode, we use the
Application.ThreadException to handle errors.
Now in debug mode, periodically I get errors (mostly SQL Server errors
because of typos in query strings) that error back to the Application.Run
line instead of the line happened. Really really frustrating, but I can
live with it if I must.
However sometimes (not all, but more than half) of any SQL Exceptions that
get thrown in release mode don't get caught by Application.ThreadException
and the application jsut disappears off of the person's screen and they have
to restart it and we don't get any information.
I thought at first it was because the SQL errors were being thrown in a
separate DLL (that is strongly referenced) but that doesn't appear to be
correct. It also happens when filling a Data Adapter on a form in our
application directly.
Anyone have any ideas as to why this is happening? (it doesn't seem to
happen on any other type of error, but that might be becuase most of our
errors are SQL typos, not other real big problems.)
Thanks,
James Hancock
|
Similar Threads
