Problems with START_PROCESS@

I have sent the example to your e-mail address.

I am using START_PROCESS@ in FTN95 v8.0 with no problems. 32-bit calling 32-bit, on Windows 10.

Never heard of START_PROCESS_AND_WAIT@ - how does that differ, if at all, from START_PROCESS@ where the calling program waits for the called process to finish?

They serve the same purpose and are coded in much the same way but START_PROCESS_AND_WAIT@ is for Windows (e.g. ClearWin+) applications where an internal 'temporary yield' is required in order to process the Windows message loop.

Thanks, Paul. My 'parent' application is Windows/Clearwin+ and START_PROCESS@ works just fine (The 'child' process is a command-window program). But maybe I should really be using START_PROCESS_AND_WAIT@ -- will try it and see if it runs any differently!