To avoid issues with the SCRIPT and determine if you're getting a ROBOCOPY error, you need to open a command prompt and run the robocopy command, just as if the script had executed it. It might shed some light on why the script is failing.. The idea is to divide and conquer.
Gargoyle's suggestion to use @SERROR is also valid, but may not tell you the whole story. RoboCopy (and most commands) exit with a numeric code that Kix will translate into a standard status message. Sometimes, this can result in misleading messages. Running just the robocopy command from a command prompt will tell you that it's working (or not) and if not, provide direct and meaningful messages from the app, and not those that are interpreted by Kix.
Glenn
_________________________
Actually I
am a Rocket Scientist!
