>You can't actually fire an error by just setting the Response.Status of the request. These error mappers work through ASP.NET's error handlers which occur prior to code ever reaching your page logic (well at least in the case of 400 style errors).
>
>Michel's point is right on - you need to throw an exception to make this happen explicitly, but then you could probably just redirect directly to this page.
>
>+++ Rick ---
>
Ultimately this is what I did. I simply redirected to the page. :) I think I like Michels idea better though. I think that is the more dynamic solution.
My thanks to all for the input.
~Joe Johnston USA
"If ye love wealth better than liberty, the tranquility of servitude better than the animated contest of freedom, go home from us in peace. We ask not your counsel or arms. Crouch down and lick the hands which feed you. May your chains set lightly upon you, and may posterity forget that ye were our countrymen."
~Samuel Adams
