>>Coordinating multiple VFP sessions is doable though - you need to plan ahead to let the separate instances pass messages and check each other's states conveniently.
>
>Doable=yes. Possibly beyond scope of simple understanding? probably
>

Hows this for simple? Build a table that all VFP sessions share, and as each VFP session starts up, have it assign itself a name using SYS(2015), and create a record in the table. It can use SYS(0) to figure out what machine it runs on. That goes in a second field. Now just add a flag that indicates busy or not, and a field to hold messages to the process. Simpe rule - you can only set messages when the message of another VFP instnace is empty, the system says it is not busty, and you can RLOCK() the record in question. The other machine has finished it's request when it is not busy and the message field is empty again.

Overly simplified, sure, but the example above is a running start for really doing this. It need not be much more involved.