The code was in a method called by the client when they wanted to open the TCP connection.

No, winsock.connect doesn't return anything. I think the winsock control is supposed to be event driven, so when you call connect it updates the winsock.state property to reflect that its trying to get a connection (I believe it goes to state=4). When a successful connection is made it does to winsock.state=7.

Perhaps this is the problem? It was mentioned earlier that events do not fire in a COM DLL environment, so maybe the winsock.state property is never updated?

The client code simply calls the method that contains the code from the previous message. That method waits for a while to see if the connection is made (winsock.state=7), if it is returns .t., otherwise returns .f.

I'm using this to pass a bunch of realtime communication information between what is supposed to be a transaction server object and a remote server. Not having much luck so far.

Thanks for any help Bob.

Matt

---
Is the above code in a method or in the init?

Does this.WinSock.Connect return anything to know if it was successfull?

Ok... let me see the client code. What do you use the winsock connection for once it is connected?
---