This just started to happen today. I am writing a POP/SMTP client, and when I run the program it works fine, but when I try to end the program, I just get an hour glass...then VB does not respond. I found out how to fix it...but its a PITA. If i have the form open in design mode when I run then stop the program when the socket is connected, it will freeze; BUT, if i close the design form THEN run the program, it will not freeze vb when I end the program. I close the socket whenever I stop the program so that shouldnt be any problem. I also downloaded other applications that use winsock, and the same error occurs.

I re-installed VB like 3 times today, and same error. I even downloaded diff WINSCK.OCX files...and the same!

Does anyone know WHY this is happening and HOW I can fix it? Sorry for the long post...

BTW, it was working fine yesterday until I created an EXE of the program to send out to a friend.

Im using VB6, and I also have VS.NET installed. Sorry for the long post...

[JimCamel]

Are you using sockets or the winsock control?
I'm pretty sure that winsock is called mswinsck.ocx, not winsck.ocx.

Anyways, you might wanna check to see that you're not getting into some kind of infinite loop when you're unloading controls (ie the winsock control) or when the programs terminating.

Have you tried any other programs which other people have used which use winsock? Did they work? That way you can tell if it's your code or something wrong with your computer/vb/winsock.

Jim

yea..it is mswinsck.ocx

yea, i did try someone elses program...and it does the same. i think my vb sucks.