Asp transfers and includes

[Thomas Scheiderich]

I have been playing with the Server.Execute and Server.Transfer as well
as server includes.

I know that these are not all the differences, but one of the
differences between Server.Execute and Server.Transfer is that
Server.Execute will include the file into the calling file and the whole
file (Calling file with the included file) will display. In
Server.Transfer, all the first file up to the Server.Transfer and the
whole file that is transfered to will display. In Server.Execute, the
first file is still in control whereas the page that we are transfered
to will be in control. Also, in the Server.Transfer the URL will
display the URL of the first page, including any "GET" form variables.

Is there a way to do what Server.Transfer does, except if we transfer to
another page - all display from the first page is dropped. This might
be for an error, where we decide there is an error and want to transfer
to an error page and not show any of the headers or data of the first page.

Thanks,

Tom.

[Steven Burn]

Response.Redirect "somepage.asp"

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

Disclaimer:
I know I'm probably wrong, I just like taking part ;o)
Thomas Scheiderich <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...

I have been playing with the Server.Execute and Server.Transfer as well
as server includes.

I know that these are not all the differences, but one of the
differences between Server.Execute and Server.Transfer is that
Server.Execute will include the file into the calling file and the whole
file (Calling file with the included file) will display. In
Server.Transfer, all the first file up to the Server.Transfer and the
whole file that is transfered to will display. In Server.Execute, the
first file is still in control whereas the page that we are transfered
to will be in control. Also, in the Server.Transfer the URL will
display the URL of the first page, including any "GET" form variables.

Is there a way to do what Server.Transfer does, except if we transfer to
another page - all display from the first page is dropped. This might
be for an error, where we decide there is an error and want to transfer
to an error page and not show any of the headers or data of the first page.
Thanks,

Tom.

[Thomas Scheiderich]

Steven Burn wrote:

Response.Redirect "somepage.asp"

I knew about that, but in some of the articles I read, they said that
the difference between Response.Redirect and Server.Transfer was that
Response.Redirect involves a round trip to the client for the redirect
to work, where Server.Transfer does it all on the server before it send
the page to the client. Of course, there may not be a Server method
that does a redirect as Response.Redirect does.

Thanks,

Tom.

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

Disclaimer:
I know I'm probably wrong, I just like taking part ;o)
Thomas Scheiderich <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...

I have been playing with the Server.Execute and Server.Transfer as well
as server includes.

I know that these are not all the differences, but one of the
differences between Server.Execute and Server.Transfer is that
Server.Execute will include the file into the calling file and the whole
file (Calling file with the included file) will display. In
Server.Transfer, all the first file up to the Server.Transfer and the
whole file that is transfered to will display. In Server.Execute, the
first file is still in control whereas the page that we are transfered
to will be in control. Also, in the Server.Transfer the URL will
display the URL of the first page, including any "GET" form variables.

Is there a way to do what Server.Transfer does, except if we transfer to
another page - all display from the first page is dropped. This might
be for an error, where we decide there is an error and want to transfer
to an error page and not show any of the headers or data of the first

page.

Thanks,

Tom.

[Thomas Scheiderich]

Thomas Scheiderich wrote:

Steven Burn wrote:

Response.Redirect "somepage.asp"
I knew about that, but in some of the articles I read, they said that
the difference between Response.Redirect and Server.Transfer was that
Response.Redirect involves a round trip to the client for the redirect
to work, where Server.Transfer does it all on the server before it send
the page to the client. Of course, there may not be a Server method
that does a redirect as Response.Redirect does.

BTW, the other difference I noticed was that the URL is the page you are
redirected to, whereas the URL is the original page that called the
System.Transfer.

Thanks,

Tom.

--
Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

Disclaimer:
I know I'm probably wrong, I just like taking part ;o)
Thomas Scheiderich <tf*@deltanet.com> wrote in message
news:40**************@deltanet.com...

I have been playing with the Server.Execute and Server.Transfer as well
as server includes.

I know that these are not all the differences, but one of the
differences between Server.Execute and Server.Transfer is that
Server.Execute will include the file into the calling file and the whole
file (Calling file with the included file) will display. In
Server.Transfer, all the first file up to the Server.Transfer and the
whole file that is transfered to will display. In Server.Execute, the
first file is still in control whereas the page that we are transfered
to will be in control. Also, in the Server.Transfer the URL will
display the URL of the first page, including any "GET" form variables.

Is there a way to do what Server.Transfer does, except if we transfer to
another page - all display from the first page is dropped. This might
be for an error, where we decide there is an error and want to transfer
to an error page and not show any of the headers or data of the first

page.

Thanks,

Tom.