In that case, you can go with the poor man's DCOM (or Client/Server) solution.

Create a table that holds pending jobs. Make one of the fields the machine name so each machine knows what jobs to perform. Create an EXE that runs on those machines that periodically checks the table and performs the job. It could post the results to another table, text file or whatever. The machine that created the job in the first place needs to periodically check the status flag to see if its job has been completed by the other machine and then retrive the results.

Maybe that will help. Just a thought.

>Thanks for the info. Unfortunately, this will be installing on Win9X machines as well as NT/2K.
>>
>>Nigel,
>>Write the COM server as you normally would, but when you create it make it an EXE and access it via DCOM (e.g. createobjectex()). That way, the COM server runs locally to the machine you install it on not the machine that instantiates it.
>>
>>One quick note. Nick (and I've seen others) have had problems running DCOM servers on Win9X machines. Is the machine where you want to access the Outlook stuff on an NT box? If not, this approach may not work for you.
>>
>>HTH.