I have written an application that basically gets user settings for a batch file/ftp script to download some files.
This may take several minutes, so I am using DoEvents while waiting on the batch process to complete. However, if the user closes the application, I have also coded to kill the batch file process. Now my problem.
It looks like the batch file starts another child process, the ftp script, that does not get killed. Can I get that child process somehow in my code, so that I may kill it to?
PS - I know using some .NET component to do the downloading would be more "graceful", but I'm kindof in a hurry, and the batch files are simple to build on the fly.
This may take several minutes, so I am using DoEvents while waiting on the batch process to complete. However, if the user closes the application, I have also coded to kill the batch file process. Now my problem.
It looks like the batch file starts another child process, the ftp script, that does not get killed. Can I get that child process somehow in my code, so that I may kill it to?
PS - I know using some .NET component to do the downloading would be more "graceful", but I'm kindof in a hurry, and the batch files are simple to build on the fly.