Help! Winsock API... The damn FD_CLOSE

[Allied]

Is there a way to determine if an asynchronous socket is sending data or not? I got a problem closing socket on my server/client application, the way it's built... Does anyone can give me an example of a graceful disconnect? I know it's something like:
1.Finish sending data.
2.Call shutdown() with the how parameter set to 1.
3.Loop on recv() until it returns 0.
4.Call closesocket().
But how can i tell that my socket is finish sending data? Please help, I'm bored!

[Hashir56]

there's a Sub that automaticly triggers (like 'command1_click' ):

Private Sub Winsock1_SendComplete()

in the code box at the top w/the 2 arrow things in the fist one select the name of the winsock1 control and in the secon select 'SendComplete'. Or just copypaste:

Private Sub WinsockNameHere_SendComplete()

End Sub