RUN SELECT USING parmlist SELECT... should work just as if you
do a RUN commandfile USING parmlist
Each item in the parameter list should be separated by a COMMA
or current DELIMITER.
Say you have two parameters one is TEXT the OTHER is INTEGER
you could RUN SELECT USING .TxtVar,.IntVar SELECT varchar clause
or
RUN SELECT USING 'txtvalue',55 SELECT...
or
RUN SLECT USING .TxtVar,55 SELECT...
Adjust appropriately the parameter list as appropriate you can
have from 1 to 16 parameters
Since the passed parameters are passed to the command file as
%n-? values within the command file I would immediately assign
them to correctly typed values for example
SET VAR cmdname1 TEXT = (.%1)
SET VAR cmdname2 INTEGER = (.%2)
After set the variables issue CLEAN VAR __-__ to remove the %n
variables. the n is 1 to 16 and ? is nesting level.
As an asside you might consider creating some of of these items
as STORED PROCEDURES. With stored procedures you assign a name
and datatype to each procedure. You then don't have to type the
paramater values within the command. You would then use the
CALL procname (.parm1,.parm2) syntax.
You cn use a mixture a variable or actual values for the
parameter list of the CALL statement just as you do with the
above mentioned RUN syntax.
Jim Bentley
--- Lawrence Lustig <[EMAIL PROTECTED]> wrote:
> <<
> It
> is
> for
> calling
> (legacy
> use)
> a
> "command
> Block"
> that
> is
> a
> part
> of
> a
> "procedure
> file".
> >>
>
> Uh oh! Have multi-block procedure files been deprecated?
> What do you mean by "legacy" use?
>
>
> BTW, this syntax is in the latest help file that I checked:
>
> RUN SELECT USING parmlist SELECT VARCHAR clause
>
> --
> Larry
>
>
>
Jim Bentley
American Celiac Society
[EMAIL PROTECTED]
tel: 1-504-737-3293
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
