Greetings, folks.

Wondering if someone might be able to shed some light on this without my
having to load up 'n test it for myself.

I have a page calling another with Server.Execute, but depending on what the
outcome of some data checks on that called page is, it may need to "break
out" of the call with a Response.Redirect.

What I want to know is, will this eventually lead to memory leaks because
there's no return to the original calling page?

The environment's a "plain vanilla" IIS installation under Windows Server
2003 Web Edition.

Ultimately I suppose it's not entirely crucial that I need to use this
method; I could always break the original page into two and use
Server.Transfer to avoid the possibility of "left-overs," but I hope someone
here can state with at least a little authority whether or not this problem
might occur.

Thanks in advance,

server.execute is a dynamic include and becomes part of the originating page.  When you leave the include, you are also leaving the
original page.

part of your conditional statement which causes the exit should also close any open objects before the exit

Many thanks for that response, Paul; certainly makes life much easier :-)

Many thanks for that response, Jon; certainly makes life much easier.

And please accept my apologies for calling you "Paul" in my reply of a few
seconds ago; it's been a _very_ long few days here :-/

Pass Parameters to <!-- #Include File="file.asp" -->
How do I submit form data and change to a different page?
RS Loop - Numeric value out of range (null)
Removing obscure chars
how to get the ip address & country of the webpage visitor
How to save byte stream as binary document
asynchronous callback component
generate PDF files with ASP.
ASP error
strings with quotes in