Yep, the Winsock activeX is a little quirky. When to use the "Winsock.OBJECT.SomeProperty" and when it's ok to use "Winsock.SomeProperty". At least Microsoft documented it well <g>.

The connect method does return T/F.
Looking at my code, I did something like this:

FOR i = 1 to nTries
IF Winsock.Connect()
*Continue on
EXIT
ENDIF
ENDIF

A final word on this. If you plan to write a fair amount of socket code, you owe it to yourself to look at Catalyst's SocketWrench. The cost is around $100. It is fantastically well documented. I submitted some VFP examples to them a few months ago to add to their sample code library. All 'n all, that product has been a pleasure to work with. I won't go back to using the Winsock activeX any time soon. My .02.

-m@