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


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?)

1 Solution
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.

    If Not Socket1.Connected Then
        msWarning = "Cannot connect to the socket!"
        PNL_MSG.Caption = msWarning
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

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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