Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
to ChrisRChamberlain
- Thread starter Takusaan
- Start date
ChrisRChamberlain
Programmer
Takusaan
Apologies for not posting as intended.
There is an article at MSDN:-
HOWTO: Determine When a 32-bit Process has Completed. Q191584
which may be sufficient for your requirements.
What the code does not do is give you any control over the initial windowstate of the called Windows application, which will be a normal windowstate.
If you need control over this aspect, you will need additional functions and code, so please advise.
What you can also do with this code if ever required, is run it in a loop, adding code which will enable the user to cancel out of the process.
It will ensure that VFP only ever creates a single instance on the called windows application(s)
HTH
Chris
Apologies for not posting as intended.
There is an article at MSDN:-
HOWTO: Determine When a 32-bit Process has Completed. Q191584
which may be sufficient for your requirements.
What the code does not do is give you any control over the initial windowstate of the called Windows application, which will be a normal windowstate.
If you need control over this aspect, you will need additional functions and code, so please advise.
What you can also do with this code if ever required, is run it in a loop, adding code which will enable the user to cancel out of the process.
It will ensure that VFP only ever creates a single instance on the called windows application(s)
HTH
Chris
- Status