The quarks of Internet Controls with Windows

[Futuristic Storm]

Dear fellow programmers,

I've been writing an application that requires a socket on the internet. By doing this I have used the Winsock connect method together with .RemoteHost and .RemotePort properties. While stepping thru each line of code, the 'Dial-up Connection' box appears after executing Winsock.Connect statement without trouble. However, after making the source into an executable file, my program no longer prompts the user with the 'Dial-up Connection' box!

My machine is running Windows 95 with Internet Explorer 4 and programming in VB5 professional edition.

The program I've tried testing with is:

Private Sub Command1_Click()
Winsock.RemoteHost = "www.msn.com" 'RemoteHost can be any valid URL
Winsock.RemotePort = 80
Winsock.Connect
End Sub

I then tried testing my program on another machine running Windows 98 with IE5 and the executable program works without a hitch. That is, it brought up the 'Dial-up Connection' box each time!

Can anyone please explain why this is happening with any remedy or solutions to this problem? Any other information will be greatly appreciated.

[Zaf Khan]

It could have something to do with the amount of time the OS takes to complete the request and maybe a Doevents() somewhere might fix it

DocZaf
{;->

If it works whilst debugging but not when compiled then usually it can be remedied.

[Futuristic Storm]

In reply to my post, the cause and solution to the problem is with Internet Explorer. When tested on IE4 the executable file didn't work at all. But with IE5, the program works every time.

So I experimented with upgrading my old IE4 to IE4.01 with the Service Pack 2 and my executable worked like a dream!!!

I would suggest to everyone programming internet based programs to upgrade their Internet Explorers to at least version 4.01 SP2!!!

Regards,

Storm