Type mismatch when using Server.Execute?

Whe I replace: <!--#include file="utility.asp"-->

With

<% Server.Execute "/dev/1/utility.asp" %>

I get a 'type mistmatch error on my connection string 'GetConnection'.

Why would this be so if server.execute is including the same file as the
include file in the same directory...?

Thanks
Jason

[Aaron [SQL Server MVP]]

> Whe I replace: <!--#include file="utility.asp"-->

>
> With
>
> <% Server.Execute "/dev/1/utility.asp" %>

You realize those are not necessarily the same path, right? Why did you add
/dev/1/ to the server.execute call?

> I get a 'type mistmatch error on my connection string 'GetConnection'.

I think you're confusing the roles of #include vs. server.execute.
Server.Execute goes out and runs a script file. Any variables created there
are not kept in memory and the resuming portion of the calling script is not
going to be aware of them.

My suggestion: stick to #includes, you're using those for the right reasons.
I don't think you're sure why you even changed it from #include to
Server.Execute.

--
[url]http://www.aspfaq.com/[/url]
(Reverse address to reply.)

[Jeff Cochran]

On Mon, 9 Aug 2004 12:20:21 -0400, <jason@catamaranco.com> wrote:

>Whe I replace: <!--#include file="utility.asp"-->
>
>With
>
><% Server.Execute "/dev/1/utility.asp" %>
>
>I get a 'type mistmatch error on my connection string 'GetConnection'.
>
>Why would this be so if server.execute is including the same file as the
>include file in the same directory...?

The simple explanation is that something in your utility.asp needed
something in the asp file that included it. By doing an execute you
don't have that soemthing.

Now as to what that something might be, we couldn't tell without some
code, which you didn't provide.

Jeff

Ok, they are the same path, I was experiment with relative and virtual
paths...

The reason I attempted a server.execute was based on the possibility of my
other sub-domains on the same server consuming this file..

However, I realise a virtual include is probably the best route as it
appears from what you told me that I cannot carry declared variables over to
the file that consumes it, right?

- Jason

"Aaron [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:eMfhusjfEHA.720@TK2MSFTNGP11.phx.gbl...

> > Whe I replace: <!--#include file="utility.asp"-->
> >
> > With
> >
> > <% Server.Execute "/dev/1/utility.asp" %>

>
> You realize those are not necessarily the same path, right? Why did you

add

> /dev/1/ to the server.execute call?
>

> > I get a 'type mistmatch error on my connection string 'GetConnection'.

>
> I think you're confusing the roles of #include vs. server.execute.
> Server.Execute goes out and runs a script file. Any variables created

there

> are not kept in memory and the resuming portion of the calling script is

not

> going to be aware of them.
>
> My suggestion: stick to #includes, you're using those for the right

reasons.

> I don't think you're sure why you even changed it from #include to
> Server.Execute.
>
> --
> [url]http://www.aspfaq.com/[/url]
> (Reverse address to reply.)
>
>