Has anyone gotten WebFOCUS 4.3.6 to run in IE7? I am using -HTMLFORM tags to generate pages and the server times out when trying to do so. It works fine in IE6 and the most recent version of FireFox.

This message has been edited. Last edited by: Kerry,

Hi,

Are you using CGI calls?
We used to have this problem prior to WF upgrade to servlet.

What we found out was there was some extra stuff in the registry (from windows patching/upgrade) that caused the problem.

Not sure if this is the same problem that you are experiencing, but if you go into your registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform
and search for .NET CLR 3.0.04506.648 delete it, close all browsers and try again.

NOTE: Before you delete anything in the registry, please back it up first in case anything fails.

Hope that helps.

Best Regards,

Jimmy Pang

Jimmy, is that something that has to be done in the WF Client Web server or in every client PC that needs to access the reports?

Hi,

I need to do that on the client PC unfortunately (was a temporary solution until we upgrade to 7.6.10 with servlet calls).
Any PCs that have the few patches installed in windows.

So I would say to start upgrading to the newer version of WebFOCUS as CGI calls won't be support soon I think.

Best Regards,

Jimmy Pang

Yes we are using CGI calls. Does IE7 not support them?

All I can say is 4.3.6 (circa 2001)? Ouch!! You can ride your bicycle in the middle of the freeway too, but I wouldn't advise it. You're going to be hard pressed to find anyone that is doing ANYTHING with a version that old. You won't even get an answer from IBI on that one.

I tried searching for browser support on your product but based on this: Web Browser Support for WebFOCUS, WF 4.3 is not even listed!

quote:

Ouch!!

I felt something similar when I saw the version of WF Mike has to support right now, and to think that I used to feel a bit bad myself because I was still working on the "old" WF 5.3.4.

I realize that working on this or that version of the product is something over which we don't always have any control. In my case, 5.3.4 is the environment my current client has and even though there is awareness about some of the interesting features we're missing out by not migrating to WF 7.6 it has not been compelling enough to motivate a change. Internal policies? Budget restrictions? who knows! It is what it is as some say

One can only hope that, if the whole technology is changing within the organization ("finally" having IE7 in the client PC, for instance) and due to that change some implemented solutions are no longer working as required, then that should be an enough reason to justify a whole platform upgrade even if the cost is high (in terms of price and effort).

Darin's point about the provider's support is extremely valid and one that cannot be taken lightly. I just cannot imagine what would happen if either box where the webserver and/or Reporting Server sits needed an "emergency" OS patch and all of a sudden WF stopped working altogether ... arrggh!

This message has been edited. Last edited by: njsden,

Yes, it's true. We started getting more and more problems with server upgrades and compatibilities with the 4.3.6 that we had no choice but to upgrade.

But it's a good thing =) You get to use the new features in the latest releases.

In answer to your original question, IE7 probably does not work with 4.3.6. IE8 caused problems with 5.3.2.