Disconnect Problem

[Lenny]

Whenever I have a procedure with the disconnected command in it like wnsck.close
it always gets disconnected first...Any fixes?

[Soul Taker]

Post some code please as I don't quite follow you.

[Lenny]

Its just that any procedure i make it always seems to skip straight to the disconnect before doing the other commands

[CrAz3D]

Post some code please as I don't quite follow you.

This might actually help, having some of what you're doing.

[Nub]

Try adding a DoEvents before you close the socket

Example:

Code Select Expand


Socket.Senddata "blah blah blah im leaveing bnet... blah..." & VbCrLf
DoEvents
Socket.Close

Hope that helps...

[Lenny]

Like
Cleanslatebot1.Send "Disconnected by " + User
Cleanslatebot1.Disconnect

It seems to disconnect first.....

[hismajesty]

are you doing CSB? If so why did you post about winsock? Um...heres my code that seems to work fine....

Code Select Expand

Private Sub disc_Click()
AddChat "Disconnected " & vbNewLine, vbRed
CleanSlateBot1.Disconnect
Form1.lvChannel.ListItems.Clear
End Sub

[Lenny]

The same problems goes for winsock
it seems to disconnected before sending the text to bnet...Is there some order of precedence I should know about between sending data and disconnecting?

[Camel]

I hope you realise Nub already answered the question...

[Lenny]

Any other way...that doesnt seem to work...

[Camel]

Don't close it until the SendComplete event to fires.

[planterspeanuts]

Don't close it until the SendComplete event to fires.

[Camel]

Don't close it until the SendComplete event to fires.

-to

* Camel sighs