Erik,

>>Clip...
>
>All this being said, Christof and Kenneth have shown that I was too quick to assert that multiple threads would be required for Kenneth's request. After looking at Christof's suggestion, I played around and successfully implemented a single-threaded server that starts a timer, returns control to the caller, and has the timer set an object property with the results of the query. This way the client can poll the server for results, and cancel if he chooses.
>
>>...Clip

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).

Had a brief thought about implementing the UI class as an ActiveX,, which would allow any front-end to call my COM servers, but this won't likely happen soon.

We will be crash-testing pretty hard today. Thanks for the conversation, it really sped things along.