Server.Transfer is a lot more overhead, but if you need to carry along all the Request values from the redirecting page it's the only way.<BR><BR>Personally, I don't understand the point of redirecting. If the form is done, why can't you just display whatever the next thing to be displayed is right in that page. But I know that many prefer separating form processing from (especially) HTML display. And of course if the next page is HTML then there is zero point in using Server.Transfer.<BR><BR>
Basically I have a page which uses an include file, to check a session value.<BR><BR>If the value is null then it shows a registration form and a value is assigned to the session once the form is completed succesfully<BR><BR>If the value matches one that is in the db then it shows information sheets they can request.<BR><BR>Basically once the form is completed, I want to transfer them back to the page where the session value is checked.<BR><BR>I think I probably only need to use a response.redirect but couldn't remember generates the most overhead.<BR><BR>A second point is, that if I am going to transfer them I want to show a message before they are transferred and then transfer them after a pre-determined amount of time. <BR>- Is there a timer function in ASP?
...and it wouldn't work, anyway!<BR><BR>You can't "PUSH" content from the server. You can *ONLY* respond to requests from the browser. Period. Basic HTTP protocol rules.<BR><BR>SO in your case, you want to simply return some HTML that has a META REFRESH tag in it or which use a JS setTimeout to trigger the next page. You don't want either Response.Redirect or Server.Transfer.<BR><BR>