>> I seem to be having a similar problem, except the
>> send seems to complete eventually without any
>> additional activity. My server app responds to
>> several client apps. The problem seems to occur
>I was just glancing through when I saw this...
>I had similiar problems as well. I think its due to the fact that winsock
>is somewhat blocking.
>Even when you have multiple sockets controls on the form. Try this instead.
>Remove the control (ocx) from your tool box. Go to program references and
>browse for the component, but look for OCX,
>look for MSWINSCK.OCX and add it. Now you can code the control directly in
>your own objects.
>dim WithEvents ServerSocket as Winsock
>set ServerSocket = new WinSock
>Now you have the control directly inside your object, no need for a form.
>Also add code in the error event of your sockets. I found this to help as
>well.
>You might want to check out Catalyst.com for their socketwrench package...
>Well written socket replacement that works (I think) better than winsock,
>and it can use fast callback notifications rather than events (it can use
>both). When multiple sockets start responding, the slow event system looses
>data (I think)
>Hope this helps a little,
>David
How do you put code in the events when you create the socket this