>>>Another approach I might look into is using CreateProcess() to run a exe that will take care of the job and using WaitForSingleObject() to wait for the exe to complete the job, this way I'll know if the job was completed or not.
>>>
>>
>>Just looking back on your requirements, and thought I might ask: have you looked at wwIPstuff? It does what I think you are trying to do by wrapping Synchronous functions in WinInet.dll. You can send mail directly to an SMTP server...
>
>I think Raul needs WinSock for whatever he's doing...
>
>It's something I never really thought about but a lot of ActiveX controls
>that are using events won't work well in COM servers in general. I've always
>thought that many of the ActiveX controls (like the Inettransfer control
>and the WinSock one in particular) are overly event oriented without
>procedural, synchronous interfaces which now seems awfully restrictive
>in light of COM servers running very linear code.

At a more philosophical level, the development of GUIs and other stuff has went way too far to the interactive side, often lacking ways to do the same things programmatically. The restriction you mention is probably just one of the consequences of this approach. So, we come to a paradoxical situation, where we must do some things manually (click or type) because we can't do them programmatically... and the computers were supposed to do things automatically, right?