While I'm not able to assist with your specific problem, I can offer a suggestion: If you keep running into problems with MS Winsock, you may want to have a look at Catalyst's FreeWare SocketWrench, available at http://catalyst.com/.

There're several code samples on the site, and they've set up an NNTP server for community discussion and support.

p.s. On SocketWrench's server side, make sure you've got the Blocking property set to .F., or the Accept() event won't fire.



>Here is my problem. The problem fails in VFP7 and 8. So I don't think it is a VFP problem.
>
>I dropped 2 winsck controls on a form. One for listening and the other to recieve the events. If you connect using Hyperterminal from one machine to the other everything works fine, until you disconnect and try to reconnect from the client end. The winsck control begins firing the error event over and over chewing up 100% of the processor. The problem is do not know the other end disconnected so I can not kill the object until a specfied time. I have tried everything, even setting autoyield=.T./.F. nothing works.
>
>I think it is a bug in the MSWINSCK control, but I can not find any listing on MSDN. The control just starts firing the events over and over again.
>
>Does anyone have any ideas?
>
>Thanks,
>Dale