>we are changing direction - to out of process exe. we are useing the FindWindow & the SendMessage API calls. do you know what other messeges we can pass? like DBClick so we can triger an event on the remote session.. i now the close x10 works fine...

You're complicating this far beyond your needs; MSMQ can provide reliable, flexible messaging for you application via an ActiveX interface, which should havemore than adeqaute performance for your needs. There's a great whitepaper by Randy Brown in the MSDN Library "Using MSMQ with Microsoft Visual FoxPro 6.0"; it's also available on-line at Using MSMQ with Microsoft Visual FoxPro 6.0 on the MSDN OnLine site.

Your messaging mechanism could be as simple as using a shared table to pass requests and post replies and results, depending on your requirements. This allows the simple creation of job server pools from otherwise idle machines in a 'fire and forget' fashion - I use this to have free systems run reports during our end-of-month process - just write a list of things that need dooing,and have a simple app thatlooks tosee what hasn't been started yet, checks tomake sure it is capable of doing it, and grabs it, maring it as 'in-process', and 'done' on completion. From my POV, I only care that all the jobs run to completions for this example - I can check the 'jobs' file at anytime to see what's going on.