> Any wise shoves in the right direction would be graciously appreciated
If you need to wait for the other process to finish why not stick the code in the same process? Once case I can see is that I use a similar technique for modifying records outside of a transaction when the method is inside of a transaction. However I use process variables and the SET PROCESS VARIABLE command instead of using process state. // Calling process fDone:=false $l:=new process(“DoSomethingCool”;0;”SomethingCool”;current process) Repeat delay process (current process;5) until (fDone) //Something Cool Process ... Do something cool … then SET PROCESS VARIABLE ($1;fDone;True) // $1 = calling process number, set the fDone in that process to true Delay process($1;0) // Un-delay the calling process However with the new SUSPEND TRANSACTION command http://docs.4d.com/4Dv15R5/4D/15-R5/SUSPEND-TRANSACTION.301-2937406.en.html <http://docs.4d.com/4Dv15R5/4D/15-R5/SUSPEND-TRANSACTION.301-2937406.en.html> (4D v15r4 and above) It will be much easier to do something like this SUSPEND TRANSACTION // Do something cool outside of transaction RESUME TRANSACTION -- Neil Dennis 4D Developer since 1990 GreaText - Designing Software for the Way You Work 716 East 1850 N North Ogden, UT 84414 mailto:[email protected] http://www.greatext.com/ ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
