>I've ended up with two classes, one is the UI element, which I call a Job Controller. The other is a COM class, which I call just a Job class. The COM class has methods such as "SetupJob", "StartJob" and "CancelJob". The UI Class has a start button, a cancel button, a list to display results, and a couple of properties to tell it which COM server to call. It's also got a parameters array that gets passed in SetupJob (if necessary for that job).
>

BTW: The March 99 FoxTalk had an article about this topic... If I remember correctly they used a Timer...

I think though, now that we have VFPCOM.DLL to bind events, the MSMQ might be more workable thing to look at. You can not only have the server pass results via MSMQ, but you could also have the server check for messages from the client to cancel it's job.

BOb