Inet problems (Follow up to failure to exit program)

[Janitor]

Earlier I posted about a problem with my program continually freezing during its unloading. Thanks to some good responses, I've narrowed the problem down to the Inet control.

Here is my new dilemna, I can't seem to fix this. According the Microsoft Knowledge Base, this problem was known to exist in Visual Basic 5.0, pre Service Pack 3. However, I am running Visual Basic 6 with Service Pack 3, making this information of no help to me.

I've tried cancelling the control, but this did not work. One thought I had was to try to eliminate the control on unloading, but I need some instruction on this.

Also, if anyone has any additional ideas, they (the ideas) would be cherished forever. Thanks for the continued help.

I had the same problem that only occurred on NT sp3,4,5, and still in 6. I've searched high and lo for a fix to the problem and nothing. This may or may not be something you want to do but my work around involved using a microsoft wininet sample app for vb, for information on the wininet api, and writing a dll based on wininet. Worked like a charm and it's really a lot easier than my initial fear of working with the wininet api. Today(hopefully) I'm actually finishing up the production dll code that will be implemented by an NT service. It doesn't do anything fancy, just what I need it to do which is ftp files without dropping a control on a form and without generating worthless errors. If anyone wants I can provide more info on this.