This fixed my argument problem, but previously I used:
-command -wait fc "%filepath%%newmd5file%" "%filepath%%md5file%" >%filepath%%fcresult%
and it worked with no spaces in the fcresult. However, now it will not dump in to the file. I have tried:
>"file",
">file", and
>file
By comparing the files and emailing the result to myself, I can verify the file is complete.
If there a way to act on the return code? Incidently, I get return code(0) when I test these files, because they match. If they do not match then I get a different return code. If I could call another function based on return code then I could email myself a success or fail email.
Thanks, Charles
_________________________
Charles McKinnis
cmckinnis@revantine.net
Cisco Certified Network Associate
CompTIA Network+
CompTIA A+