Hi Roman,

How does it work ? Could you implement it instead of MS Winsock with a minimum change ? If there's same method and event it seems just cut and copy the code ?
We create Electronic Cash Server (ECR) for our super markets application. All Cash registers have interface module and communicate with server computer through Serial port using MSComm control. This ECR Server communicates with VFP application, which manages database operations, through WinSock control. That was the reason to try to use Winsock ActiveX control to make TCP/IP communication.
MS Winsock is VB ActiveX and work without any problems in VB, because it allowed Method and Events with the same names. In VFP this is forbidden We create as I explained in previous e-mail VB wrapper that avoid VFP restrictions. This control can be used in VFP5.0.6.0, 7.0 applications, as well in applications, written in other languages.
I'm just tried SocketQ, which seems working fine (more than 240 simultaneous thread without problem, and real multitask).
In reality this is the same MS Winsock control (with the same features, possibilities and restrictions, which are well explained in MSDN Help and articles), but wrapped. We only change the names of the Events, which double methods names. These are CLOSE become ConnectionClosed Event and CloseConnection Method; CONNECT become Connected Event and SetConnection Method
How do you distribute it, what does it need to work, just Winsock1.1 or does it working with Winsock2.0, could we test it ?
We distribute it as a OCX. It works with Winsock2.0. You can use MSDN help