Executing a routine in parallel with itself 1

[joeschoe]

I need to send multiple files to a server. I use ftp and a statement like
RetVaL = ExecCmd("ftp -n -s:ftpparam ftp.myserver.com")
it takes 20 seconds to initialize the handshake etc on the ftp server and upload even a small file. I tremble to think what would happen with a 2 Meg file.
I would like to either find a faster way to upload, or let the ftp (or alternate) procedure carry on at its own pace while my system continues.
I could even envisage multiple uploads in parallel.
How do I make the call to the ftp routine in such a way that the processing carries on without waiting for completion?

 

[Glasgow]

What is ExecCmd? Your own routine?

If you were to use the Shell command would that not give the desired result - i.e. kick off the ftp without waiting around?

 

[joeschoe]

Thanks Glasgow, you reminded me why I used ExecCmd in the first place.
ExecCmd was a routine I got off the web somewhere specifically to wait for completion of the shell command. I forgot why I used it (2 years ago) and it became a standard part of my core code.
Looks like I have to document my code better for my own use.

 

[strongm]

ExecCmd was an early Microsoft stab at a version of the ShellAndWait functions we've illustrated in this forum on a number of occassions; I think ShellAndWait is a far more descriptive name for what actually happens than ExecCmd