Winsock.ocx problems

The supplied winsock ocx with Vb6 has a fault that maybe (I HOPE) can be resolved.

This bug is when i get the control to send a msg to a bunch of users ie winsock1(num).senddata in a loop after someone IE say winsock1(56) sends a messsage. The problem is that sometimes only the sender recieves the message and the others dont get the data.
Why is it so?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Try doing a DoEvent after you send your data...


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
exnAuthor Commented:
How does one USE the do event command?
Like this:

   winsock1(num).senddata "Hello" & VbCrLf

exnAuthor Commented:
Thankyou. That has saved me hours of trying to sort it out.
It baffles me as to why this has to be done
Glad I could help you!

Basically what is happening is the the SendData request is sent to the winsock OCX but the winsock OCX doesn't send the data until the VB program releases the processor...


It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Programming Languages-Other

From novice to tech pro — start learning today.