I am using winscp.com via command line.
I am preparing a batch script (winscp.com /command "command1" "command2" "etc.") from within VBScript and executing it (Shell.Exec) and trying to catch the exit code.
When there are errors (Ex: file not found, invalid command, etc.) within the session, the exit code returned stays as 0 regardless of how many errors are there.
NOTE: I have the batch mode set to: option batch abort which should return a non-zero exit code for errors, and still this issue occurs.
Please let me know what could be causing this and how to correct it.