>I downloaded VFPCOM but can't see the use of it to solve my problem.
>The only thing I found that could be of use to me is the BindEvents() function, but as I understood from the docs it is used to bind an event in an automation server to a method on my class. The Winsock control is not an automation server (am I right?) and even if it was the problem would persist as the Winsock control would be idle while waiting for data.
>

No, an ActiveX control is an OLE Automation Server, and there may be events in the Winsock control that can't be wrapped directly with VFP code without the use of VFPCOM's BindEvents methods. You can create an instance of the Winsock object independent of a form. Unless there are events that are a part of the Winsock object that you want to wrap with VFP code, VFPCOM isn't going to do anything in particular for you. If there are events that are a part of the Winsock control that you wish to have trigger VFP code, you can construct the necessary wrapper from the ExportEvents skeleton class, and use that to create a VFP native object that is bound to an instance of the Winsock control by an instance of VFPCOM.

>I'm about to give up on this one (something I'm not use to <g>).
>These are the times when I really wish my customer was using Linux with Apache or anything else but NT/IIS. ;)