Pass Parameters to

What is the workaround of passign a parameter to any included asp
file:



This obviously does not work:



Thank you

Jon
Tue Apr 03 11:45:06 CDT 2007

Server.Execute Method

The Execute method calls an .asp file, and processes it as if it were part of the calling ASP script. The Execute method is similar
to a procedure call in many programming languages.

http://msdn2.microsoft.com/en-us/library/ms525849.aspx

<vunet.us@gmail.com> wrote in message news:1175617499.385520.188400@n76g2000hsh.googlegroups.com...
> What is the workaround of passign a parameter to any included asp
> file:
>
> 
>
> This obviously does not work:
>
> 
>
> Thank you
>

vunet
Tue Apr 03 11:55:50 CDT 2007

On Apr 3, 12:45 pm, "Jon Paal [MSMD]" <Jon nospam Paal @ everywhere
dot com> wrote:
> Server.Execute Method
>
> The Execute method calls an .asp file, and processes it as if it were part of the calling ASP script. The Execute method is similar
> to a procedure call in many programming languages.
>
> http://msdn2.microsoft.com/en-us/library/ms525849.aspx
>
> <vunet...@gmail.com> wrote in messagenews:1175617499.385520.188400@n76g2000hsh.googlegroups.com...
> > What is the workaround of passign a parameter to any included asp
> > file:
>
> > 
>
> > This obviously does not work:
>
> > 
>
> > Thank you

so will this work?: Server.Execute myfile.asp?id=123

Jon
Tue Apr 03 12:22:36 CDT 2007

no, you don't need to pass anything through.

The external file is processes information as though it is part of the originating file.

Therefore any values in the originating file (id=123) can be used by the external file.

vunet
Tue Apr 03 13:26:11 CDT 2007

On Apr 3, 1:22 pm, "Jon Paal [MSMD]" <Jon nospam Paal @ everywhere dot
com> wrote:
> no, you don't need to pass anything through.
>
> The external file is processes information as though it is part of the originating file.
>
> Therefore any values in the originating file (id=123) can be used by the external file.

Do you say I cannot use params at all?

Jon
Tue Apr 03 13:40:56 CDT 2007

params aren't required with this solution, please read the instructions for usage at the site link provided.

<vunet.us@gmail.com> wrote in message news:1175624771.487195.216760@b75g2000hsg.googlegroups.com...
> On Apr 3, 1:22 pm, "Jon Paal [MSMD]" <Jon nospam Paal @ everywhere dot
> com> wrote:
>> no, you don't need to pass anything through.
>>
>> The external file is processes information as though it is part of the originating file.
>>
>> Therefore any values in the originating file (id=123) can be used by the external file.
>
> Do you say I cannot use params at all?
>

Anthony
Tue Apr 03 15:15:55 CDT 2007

<vunet.us@gmail.com> wrote in message
news:1175617499.385520.188400@n76g2000hsh.googlegroups.com...
> What is the workaround of passign a parameter to any included asp
> file:
>
> 
>
> This obviously does not work:
>
> 
>
> Thank you
>

Is the file being included expecting to be able to read parameters from the
querystring?
Can it be independantly visited by the client or is it always intended to be
an include?

vunet
Tue Apr 03 16:06:47 CDT 2007

On Apr 3, 4:15 pm, "Anthony Jones" <A...@yadayadayada.com> wrote:
> <vunet...@gmail.com> wrote in message
>
> news:1175617499.385520.188400@n76g2000hsh.googlegroups.com...
>
> > What is the workaround of passign a parameter to any included asp
> > file:
>
> > 
>
> > This obviously does not work:
>
> > 
>
> > Thank you
>
> Is the file being included expecting to be able to read parameters from the
> querystring?
> Can it be independantly visited by the client or is it always intended to be
> an include?

i've decided using this strategy:
dim id : id=123

id=321


where file.asp will assign id value to appropriate object.
yes, i do need to use some kind of include method

Dave
Tue Apr 03 17:06:01 CDT 2007

vunet.us@gmail.com wrote:
> i've decided using this strategy:
> dim id : id=123
> 
> id=321
> 
>
> where file.asp will assign id value to appropriate object.
> yes, i do need to use some kind of include method

This is an especially inefficient way to use include files. You would be
better served by putting the applicable parts of the include into a Sub or
Function, then call them with the respective IDs:

[------- Begin file.asp ----------]
Sub DoStuff(id)
{ your included code goes here }
End Sub
[-------- End file.asp -----------]

As long as everything in the include is in functions or subroutines, you can
place it anywhere in your document and make the calls where you need them.

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

vunet
Wed Apr 04 09:42:55 CDT 2007

On Apr 3, 6:06 pm, "Dave Anderson" <NYRUMTPEL...@spammotel.com> wrote:
> vunet...@gmail.com wrote:
> > i've decided using this strategy:
> > dim id : id=123
> > 
> > id=321
> > 
>
> > where file.asp will assign id value to appropriate object.
> > yes, i do need to use some kind of include method
>
> This is an especially inefficient way to use include files. You would be
> better served by putting the applicable parts of the include into a Sub or
> Function, then call them with the respective IDs:
>
> [------- Begin file.asp ----------]
> Sub DoStuff(id)
> { your included code goes here }
> End Sub
> [-------- End file.asp -----------]
>
> As long as everything in the include is in functions or subroutines, you can
> place it anywhere in your document and make the calls where you need them.
>
> --
> Dave Anderson
>
> Unsolicited commercial email will be read at a cost of $500 per message. Use
> of this email address implies consent to these terms.

so if I have 4 pages I normally "include" now, you suggest to combine
them into one page each within a sub? that will be a loooong code
page. what is "inefficient" about my method above? i understand that
may not be the best way, but i want to know how it make things worse.

Dave
Wed Apr 04 14:33:08 CDT 2007

vunet.us@gmail.com wrote:
> so if I have 4 pages I normally "include" now, you suggest to
> combine them into one page each within a sub?

Not at all. I am saying there is almost never a benefit to including the
same file twice in the same script. To extend my example to your original
one, instead of this...

dim id : id=123

id=321


...use this:

 (with Sub defined)
DoStuff 123
DoStuff 321

> what is "inefficient" about my method above? i understand that
> may not be the best way, but i want to know how it make things
> worse.

The parser will fetch a copy of the included file for each #include
statement and splice it into the script before parsing a sigle line of
VBScript. Your approach could add a tremendous amount of redundancy.

As for your concerns about the length of code, my suggestion actually
shortens it.

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.

Pass Parameters to

Re: Pass Parameters to  by Jon

Re: Pass Parameters to  by vunet

Re: Pass Parameters to  by Jon

Re: Pass Parameters to  by vunet

Re: Pass Parameters to  by Jon

Re: Pass Parameters to  by Anthony

Re: Pass Parameters to  by vunet

Re: Pass Parameters to  by Dave

Re: Pass Parameters to  by vunet

Re: Pass Parameters to  by Dave