• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 225
  • Last Modified:

Winsock-Handling

I try to establish a TCP/IP-Connection with the VB5-winsock-control.
If the connection fails, my winsock_error-event is called in Windows NT (that's what I want), in Windows 95 I get a runtime-error and my event-handler is ignored. WHY?

(By the way, how can I set then send- and receive-buffer-size?)

Thanx!
0
meik
Asked:
meik
1 Solution
 
joe_sCommented:
I'm using the Catalyst SocketWrench control and I'm not having that problem. I assume you have code in the error event????
I forget the site but Catalyst has a WEB site where you can D/L the control. I'm using the following code, I can bring down the socket server on the remote site and my _LastError event is fired. I've had no problems at all with the Catalyst control.

    Socket1.Connect
   
    If Not Socket1.Connected Then
        msWarning = "Cannot connect to the socket!"
        Display_Warning
        PNL_MSG.Caption = msWarning
        .
        .  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now