Dmitry,

Thanks for tip. It now works!


>Hi!
>
>It's pity you don't read the messages attentively.
>You should use winsock.object.connect() to connect the server, not winsock.connect()
>Didn't I write this?
>
>>
>>I've also tried using the connect method of mswinsock in vfp6
>>
>>example
>>.connect("www.webintel.net",80)
>>
>>then i checked for the state
>>.state
>>
>>but nothing happens. State always returns 0. In VB it mswinsock connect works. Maybe vfp6 can't distinguish if connect is an event or method?
>>
>>
>>>Hi, Pavel
>>>
>>>>From telnet.exe it works. (Address 10.1.220.1 or 127.0.0.1, port 2001)
>>>>From second form, no.
>>>
>>>I've looked through your code and found what's not correct.
>>>Unlike FoxPro classes ActiveXes can have methods and events with the same name.
>>>VFP6 gives us a possibility to use both methods and events. It "adds" the "object" property to the OLE object sintax. MSWinsock.Winsock have both Connect method (we invoke it in order to initiate a connection) and Connect event (it fires when connection is established). So, inside VFP yourtcpobject.Connect means "run code placed in Connect event". And yourtcpobject.object.Connect means "invoke Connect method".
>>>
>>>So, it's anoter reason to upgrade, isn't it?