Whats your config so we know what it works on.
Printable View
Whats your config so we know what it works on.
It's nothing too spectacular - it's running Win XP Pro SP 2 on a fairly ancient HP Pavillion laptop ...
Just came from MS and they had no record of ieframe.dll !Quote:
Originally Posted by BruceG
I did get it thru another source for dlls, but vs. 7.0.5346.5 and not the one you suggested.
Hang on, you are missing the point. We are talking about backwards compatibility NOT building a new app with the new dlls that IE7 provides as Bruce has done. Please don't confuse the issues, this is still broken, and MS have just put out IE7 as a Windows Update today, so it's about to get very much worse!
True. I took a VB6 class in 1998 when it was brand new...and didn't touch VB6 between then and now!Quote:
Originally Posted by RobDog888
RobDog, slightly off-topic...we're still developing a brand-new app in VB6 because I was told it would 'take too long' to get VB.NET installed and nobody on the team has .NET experience; I'm the only one who can sort of program VB, which is scary.
What's the absolute maximum time (in your opinion) that we can wait to migrate to .NET? I'm worried that if we don't do it now it'll never get done and the app will stop working with the next major Windows release because none of these guys are .NETers. I could maybe fumble my way through migrating this app to .NET, with a lot of help from you guys (insert angelic smile here). Is this making any sense? In a nutshell, I'm concerned about developing in VB6. I've always thought we should have gone the .NET route to begin with but I was overruled and I think we're on a small amount of borrowed time. What do you think? :eek:
To get back on topic, I feel your pain that this "breakage" has occurred on your systems, and I was quite concerned when I read this initial thread, which prompted me to do the testing.
As I mentioned before, I was able to run an existing compiled app after IE7 was installed, and I was able to use the WebBrowser control on a new VB6 project on that same machine.
To Ballistix's last point, I did another test last night, where I opened the project for the existing app in question, and again to my relief there were no issues when I opened the project. I also ran the app in the VB IDE without issue. (Ballistix, does this last test address your point, or is there another test I should do?)
Needless to say, this is a relief for me (so far). I am just reporting my experience here to add to the body of knowledge regarding this problem.
I'm currently using C:\Windows\System32\shdocvw.dll for Microsoft Internet Controls ...
It works fine, I do get debug messages from VB in debug mode, but at run time they don't appear.
I hope it helps ...
---------------------------------
My System
Windows XP Professional SP2
Visual Basic 6 SP6
Internet Explorer 7.0.5730.11
Yesterday i reported problems with IE7 but it was beta built.
Today i updated to full IE7 version and all errors vanished.
Could you provide me code snippet so that i can test to say whether it works in IE7 mature version or not?
Thank You.
EASY FIX
In IE7 browser settings. enable scripts
also be sure to reference ie6 and include controls for the ie6 version with your installer.