Yes, that is what it means, and it does kinda suck...
Dim x
x = 3
Server.Execute "somepage.asp"
-----
somepage.asp:
Option Explicit
Response.WRite x
-----
result:
Variable not declared 'x'
You can kinda do conditional includes. You can do:
Dim x
x = 3
Select Case x
Case 1 %>
<!-- #include file="file1.asp" -->
<% Case 2 %>
<!-- #include file="file2.asp" -->
<% Case 3 %>
<!-- #include file="file3.asp" -->
<% Case Else %>
<!-- #include file="else.asp" -->
<%
End Select
'...
%>
But, with that, all of your files are actually included. It's just that the
code only in one of them will be executed.
Ray at work
"Pietro" <pe******@nowhere.com> wrote in message
news:r%*********************@news20.bellglobal.com ...
I read somewhere:
" Another potential drawback with Server.Execute is that any page-scope
variables are not shared between the original page and the executed page.
"
Does that mean that variables declared (with Dim ...etc) in the "mother"
page are not passed to the "included" one?? That'd might be a problem.