Rick mentioned that the Application_Error method is Autowired in one of his posts. I may have misled you earlier by saying that you have to hook into that event. If you still have the Error += new EventHandler... in your global.asax, remove it. I would also comment out the redirect and just write a message out instead, and put a breakpoint on that line as well to verify that it is firing. I tried with a simple new web app by putting some simple code in the App.._Error method and putting a throw new Exception("test"); in the Page_Load.

I know it is something little we are just missing. Try that, then maybe in 10-15 minutes, you can be implementing Ricks full featured handler. (That was pretty nice, eh? Haven't spent enough time on West-Wind since the new dotnet stuff came out.)

Guess we will need a new "DotNet Applications with Visual FoxPro 8.0" to supplement "Internet Applications with Visual FoxPro 6.0"
That is the book of Ricks which I used when I designed all the client data access tools for our web site.

>What I have right now in my Application_Error is this:
>
>

>string ErrorDescription = Server.GetLastError().ToString();
>string RedirectString = "Error.axpx?ErrorDescription=" + ErrorDescription;
>Response.Redirect(RedirectString);
>Server.ClearError();
>

>
>I throw a new ApplicationException, and I get the default "Error in the application...An unhandled exception occurred" message, not the Error.aspx that I'm expecting. Obviously I want to do something more sophisticated, like log the error to an XML file or the windows event log or something, but I'm just trying to get this much working right now.
>
>If it makes any difference, the debug mode is RemoteOnly.
>
>Thanks, Bill.