-
This problem wouldn't exist in a sequential language eg 'C'
I have in install program written in VB which runs
Setup.exe from the ODK for an Accrss Run-Time database.
It alse copies a number of other files from the CD to PC.
I then need to run another Setup.exe (to install SnapView.exe), which is in a different directory from the first one, but keep getting a clash:'Setup is already running'
Obviosly VB can't differentiate between the two!
I don't expect 'Do Events' to change things and have thought of putting a 'nothing' loop in between, which seems messy and anyway I'll never know how long to set it for.
I considered continually checking for the exsistence of the last file from the first Setup.exe before running the second, but all of this seems crazy.
There must be a way of halting subsequent execution of a program until a procedure has finished.
Am I missing soimething?
-
Try renaming the second Setup.exe file to something else.
-
renaming the 2nd setup file was the 1st thing I tried -
didn't work.
-
If you use the Shell() function, it returns the ID of the new process/thread. If you loop through (using DoEvents) for this to exit, then move on, it should work.
-
Parksie
I'm confused by
'If you loop through (using DoEvents) for this to exit'
Checking the ID looks good, but I need to understand the above
Cheers
