I haven't tested this, but you could try
SET PROCEDURE TO ('procdir\proc1','procdir\proc2')
or
SET PROCEDURE TO ('procdir\proc1'),('procdir\proc2')


>The code that I have inherited is full of things like
>
>USE myTable ALIAS myAlias
>
>and then code such as
>
>SELECT 'myAlias' ---- rather than SELECT myAlias
>REPLACE myField WITH myValue IN 'myAlias'
>etc.
>
>This doesn't seem to cause any problems, but I did find a problem with a similar construct
>
>SET PROCEDURE TO 'procdir\proc1','procdir\proc2'
>
>When the project builder came across this line it only pulled proc1 into the project while
>
>SET PROCEDURE TO 'procdir\proc1'
>SET PROCEDURE TO 'procdir\proc2' ADDITIVE
>
>and
>
>SET PROCEDURE TO procdir\proc1,procdir\proc2
>
>got both of them
>
>Are there any reasons to use strings (maybe it made it more clear to him) and does anybody know of any other gotchas from using them?
>
>Thanks......Rich