Results 1 to 2 of 2

Thread: stupid winsock problem

  1. #1

    Thread Starter
    New Member
    Join Date
    Jul 2000
    Posts
    1

    Exclamation

    My problem -
    ok im using the winsock control version 6.0.8 to comunicate between to apps in vb. Both the client and the server portion are going to be run on nt. When i test them out and connected with them on my own computer they work fine, but if i put the client or server on a different comptuer on our network the client will crash. All that is happening is that the error event of the clients winsock control is firing and so the apps wont connect. How do i find out what this error is? any one have any ideas about what it could be? do i need to get an updated version of mswinsck.ocx?
    -mark

  2. #2
    Guru Clunietp's Avatar
    Join Date
    Oct 1999
    Location
    USA
    Posts
    1,844
    Hi Fish

    to display the winsock error, handle the Error event:
    Code:
    Private Sub Winsock1_Error(ByVal Number As Integer, Description As String, _
        ByVal Scode As Long, ByVal Source As String, ByVal HelpFile As String, _
        ByVal HelpContext As Long, CancelDisplay As Boolean)
    
        MsgBox Description
    End Sub
    That can help you track down your error.

    The Winsock control was also updated in Service Pack 4, so you might want to apply that as well.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width