Search results

Right...both of the lines I posted work in commend prompt. The upper one that starts with cmd.exe /C is an exactly copy of what RunCMD() debug output for the cmd variable contains. The lower one is simply a reduction of the original, as I figured the leading cmd.exe /C was redundant when entered...

I know it looks strange, doesn't it? But the full structure that debug emits does seem to make sense, or at least it could make sense. After the leading cmd.exe /C the entire string is wrapped with a pair of doublequotes, and inside that string two other strings are wrapped in doublequotes...

Two boneheads are better than one...I'll continue to experiment and will report back if any progress. It is a nice bit of code, appreciate that you put it up here.

ironfelix, thanks for posting this code, it's a real find. I am having issues and would like your input. As I've understood from your examples, one may either stuff the parameters into the Path variable, or else send as an array via ParamArray(). In my testing I've found cases where in calling...