Yup, it should trap the error at the global handler. Try this - I suspect
the global file may be corrupted - handle the appdomain unhandled exception
event from the global asax code behind or the thread unhandled exception. If
you can't catch those, I would copy the contents of the code behind/besides
file, delete and add a new global asax file and paste in the contents of the
code behind/besides file.

Signature
Regards,
Alvin Bruney
------------------------------------------------------
Shameless Author Plug
OWC Black Book 2nd Edition
Exclusively on www.lulu.com/owc
$24.99
> Hi,
>
[quoted text clipped - 28 lines]
>
> Any ideas would be much appreciated.
cashdeskmac - 11 Oct 2007 09:46 GMT
Thanks, Alvin,
I was looking into the AppDomain.Current.UnhandledException event a few days
ago but wasn't sure where to implement it (each page or in the Global.asax).
It turns out that my Global.asax was in the wrong folder (my app has over a
hundred projects, each with their own Global, but there wasn't a copy in the
root directory). I placed one there and everything works as desired now.
Thanks again,
Mac
> Yup, it should trap the error at the global handler. Try this - I suspect
> the global file may be corrupted - handle the appdomain unhandled exception
[quoted text clipped - 35 lines]
> >
> > Any ideas would be much appreciated.