I am calling it from a batchfile run on a windows 8.1 64bit desktop using the following syntax
call %WINSCPEXENAME% %PROFILE_NAME% /Script="%SCRIPT_FOLDER%%SCRIPT_FILE_NAME%" /log="%LOG_FOLDER%%LOG_FILE_NAME%"
where %WINSCPEXENAME% is WinSCPPortable.exe
winscpportable is kicking of the file download and immediately returning control back to the batch file before the file download has completed.
As the following task is a vbscript that processes the downloaded file this causes real problems.
The older non portable versions of winscp I have used
called using exactly the same commandline above from a batch file
kick off the file transfer and retain control (cmdline window stays open) until the file transfer has completed THEN returns control back to the batch file so that when the next script runs it knows the winscp part of the process has completed.
is there any switch I can apply when scripting using winscpportable to force it to retain control of its process until all the file transfers in the session have completed?
Please note the immediate return of control is NOT because I am using "call" or "start" etc in the batch file in the above example.
As our company has rules about what you can "install" on desktops I am forced to use the portable option and no I dont have access to a server.
Any Help or advice would be apreciated.
I have scanned FAQ, this forum and Google etc but not found any answers.