Don, could you consider two-record interim table, i.e. you put actual values in two or more records there and then call stored procedure which will operate with these values, i.e. no macros substitution/variable needed.

>I tried doing the sample with create procedure as @ but that didn't work.
>SQL said that there were no statements...
>
>Does SQL allow for low-level file output to an .SQL script which it can then execute?
>
>The other problem that I ran into was that you had to declare the variable you would be using in the SQL statement to initiate the process, which in this case would be of a TEXT data type. These apparently are not supported for variable declarations and wouldn't work... You would still be set to a VARCHAR of 255.
>
>Any ideas???
>
>>>Hmmmm....
>>>
>>>I was thinking of something along the lines of the following:
>>>
>>>SELECT @sqlstatement = sqlholder.sqlstatement
>>>CREATE PROCEDURE sp_tempwork AS @sqlstatement
>>>
>>>I dunno if this would work...do you?
>>
>>me too :). My guess is if some intermediate table will be involved anyway, then you could utilize two or more records of this table and then call stored procedure with few parameters (record ids).