I use Run Select all the time, and never considered passing in
parameters. Why can't you simply create a variable first that is
referenced in the procedure? That's the way I also do it.
SET VAR vWhere = 'CustBal > 0'
RUN SELECT getcustomer FROM proceduretable
The "getcustomer" procedure would reference the vWhere
Karen
> Yes, I tried
>
>
> RUN SELECT 'LiteralValue' ConvertProgram IN TableName WHERE RowID =
> 'Type2Process'
>
>
> and it doesn't work. When I do
>
>
> RUN SELECT ConvertProgram FROM StatRunSetup WHERE StatRunSetup =
> 'Type2Process'
>
>
> it works fine (although, of course, my value isn't passed in). I'm not
> entirely clear from the help file what the write syntax is for USING, but it
> clearly indicates that USING is supported.
> --
> Larry
>
>
