Hello All,
I have a WinDev server project to which a Visual Basic 6 client connects via Sockets. When I call the SocketClose function on my WinDev server, the VB client knows that a "Disconnection is Pending." If on the other hand I do not call SocketClose from my server, but click on the exit button (which only calls the Close() procedure) my VB client immediately knows that the disconnection has occurred.
Does anybody know what the Close() procedure is doing that SocketClose is not?
Thanks in advance.
Message forwarded from pcsoft.us.windev