Visual Basic 6 - Internet Explorer 8

No, that will not work, as I was trying to explain.  The reference does not work any longer.... the control does not even appear on the toolbar.

I have  internet explorer 8 although I dont use the webbrowser control I can see that on my computer the component is actually ieframe.dll

The reference points to here:
Microsoft Internet Controls (c:\windows\system32\ieframe.dll)

Thanks,
thats what it used to be on 6.  The fix for upgrading to 7 was to change it.  I cant get it to work as ieframe.dll or shdocvw.dll

I just noticed I had some difficulty as well but changing the following seemed to fix the problem. Give it a try see if it helps.

HKEY_CLASSES_ROOT\TypeLib\{EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}\1.1\0\win32

(default) C:\WINDOWS\System32\shdocvw.dll

Mine is already set to C:\WINDOWS\System32\shdocvw.dll as I changed it via the Browse button on the references window in VB.

I have tried manually settining this via your registry now, both to ieframe and shdocvw to no avail :(  It looks like its broken for good now... I'll have to see if I can revert back to IE7.

Thanks anyway.

UPDATE:

I have now reverted to IE7, and the Webbrowser control STILL does not appear in the toolbar.  I can not find a solution to this problem anywhere.

I was able to compile successfully by adding a reference shdocvw.dll and then restart VB6.

me too eventually... after my third install.  I did have the beta, I can only assume it was some residual files causing the problem?  Who knows.

IE8 is really bad, most of the time I can't get it to bring up google thats IE8 on its own! in VB6, I gave up with IE8, I just got a white screen most of the time.

In windows using IE8, used to take about 10 attempts to bring up google, it would just sit there doing nothing. Was the same in my VB6 app too.

Cure ? well I put IE7 back on, glad i did, actaully runs a lot faster then IE8! Strange thing is, a lot of people dont seem to have this problem. Though a lot of people use IE8 in VISTA and I am using XP. Can only assume IE8 does not work well in XP for some reason.

I do know a lot of others have issues with IE8 also, though ive not looked into this. Maybe a problem with IE8 just in XP. Can't really say, though overall, IE8 seems a bit of a dud. Since putting IE7 back on ive not had any problems.

People who use my software in Vista with IE8 dont have any issues overall, well assuming IE8 worked right on their PC in the first place. I really wish there was some other controls other than IEFRAME with better support and features :-(

It seems to be an install issue...

If I have IE8 on a Windows image, or install it when the computer has not much more than Windows on it yet, then it seems fine and it works with VB6 with not much tweaking.  Otherwise its random, and might be ok or full of random bugs like duplicating windows, white-screening, freezing, crashing-out and so on.

Reverting to IE7 usually solves this, but not always.

*by windows image I meant to say streamlined into a windows install disc so that it installs IE8 instead of IE7

sounds like an install / upgrade issue then, would explain why vista users who had IE8 installed in the first place never have the problem (that I know of).. ive updated from IE7 to IE8 on 2 PC's and 1 laptop that I own here, IE8 did not work on any machine. Moved to FF, but of course does not help with VB issues.. I put IE7 back on my main pc.. no problems since.. so must be some upgrade bug then it seems!

Looks like I am going to have to give up on VB6 now though...

lasted 7 years after MS dumped it for no justifyable reason at all

Ive been at VB6 on and off for a long time, you just get the hang of something and it gets no longer supported.. its why I gave up on IT work, as by the time you learn it, its outdated!  Ive not looked at VB.NET yet, presume it will have a similar function set as VB6.. though its not something im going to spend any time on now.. It takes weeks/months to program a good application in VB6 as it is, without having to re-learn something like VB.NET to do it. Not worth it in my case, as I only write applications now and then, so moving to VB.NET is not really needed for me. I guess one day I will look at it, but I guess Microsoft already have in mind stuff to replace VB.NET.. Can't say I have the time to keep up with it all either :-(