I'm using the following code to call external programs from within
RUN WinExec ( INPUT <program-name> , INPUT 1 ). /* 1=normal 2=minimized */
PROCEDURE WinExec EXTERNAL "kernel32.dll": /* Run Windows application */
DEFINE INPUT PARAMETER prog_name AS CHARACTER.
DEFINE INPUT PARAMETER prog_style AS SHORT.
It could also be done with
Windows run the program, (with the kernel32 call or the DOS call) but in
the mean time, progress continues immediately.
Is there any way I can tell progress to wait untill the called program
In our old DOS systems progress must wait, since there is no multitasking,
but in Windows 95 it tries to access files wich are not yet created, since
Windows is still busy to start the needed application.
Most of the time I promt the user to indicate when the task is completed,
but now I have a situation where the user does not interact with the called
program, which also runs minimized and terminate after the operation. On
slower machines, or when users multitask intensively, it also happen the
users respond to the prompt before the needed aplication has even started!