>WinSock have two methods with same name as two events - Connect and Close. These methods/events are necessary if you use TCP protocol. In VFP, if you call Connect method to establish connection with remote computer, you actually run code, which you are write under Connect event. Thus, establishing connection is impossible. Situation is the same also for Close method/event.

The Winsock control does work within VFP. I have used it in testing and many others here, on the UT, have used it in production.

The two different Connect and Close methods/events come from two different interfaces (IMSWinsockControl and DMSWinsockControlEvents). DMSWinsockControlEvents is exposed in the form/class designer so you can write code to run when a particular event occurs. However, if you explicitly call Connect or Close, I believe you are actually calling the IMSWinsockControl method which may or may not result in the event firing.

You may have this problem confused with another documented problem. VFP, unlike VB, can not handle ActiveX controls that have properties and methods with the same name. Mabry creates a number of controls with this issue.

Regards.