Hi Jeff ---

The & is going to work because its simple macro substitution. Using parenthesis is like EVAL() and (pure WAG here) the comma probably confuses VFP.


>There seems to be some sort of odd behavior in SET PROCEDURE where it won't accept a string variable as the argument if the string contains more than one procfile.
>
>Specifically:
>
>SET PROC TO XXX, YYY
>PUBLIC gcProc
>gcProc = SET("PROCEDURE")
>SET PROC TO ZZZ
>SET PROC TO (gcProc)
>
>This last line yields a VFP error "Invalid path or file name".
>
>However, the following works:
>
>SET PROC TO &gcProc.
>
>What gives?
>
>-- jas