Thanks Marty. The links were definitely helpful.

Based on the repeated "no buffer space is available" error, Im now thinking that the problem is with the code in the data arrival event.

I found out that the Static function retains its values even after the procedure has completed. Below, is the comment from this link http://msdn.microsoft.com/en-us/libr...t8(VS.80).aspx

"Specifies that one or more declared local variables are to remain in existence and retain their latest values after termination of the procedure in which they are declared."

However, since we're now unloading/re-loading winsock, Im not sure if the above applies. But, I made the changes below and everything is continuing to work.

The way it was...

Code:
Private Sub Winsock1_DataArrival(index As Integer, ByVal bytesTotal As Long)
 
Static AmtMessages          As Integer 'the number of messages to be loaded
Static strData1             As String  'the data of the loading message
Static strBuffer            As String  'the buffer of the loading message
 
End Sub
Now, I changed strData1 from Static to Dim and then moved AmtMessages and strBuffer to the General Declarations section and then declared them as Public instead of Static.

Ive just started another test...

Techsent