Yes! maybe there are object with expression way more complicated, but that would not be the case, it can actually be a bug with IE9 and whatever version you have of Qlikview, so please provide the version. I would also make a copy of the application, open the app, create a blank sheet and save it on that blank sheet and try to open again with IE9, and see if that opens, then go to each sheet until you get the same error, then eliminate each object of that sheet until you pinpoint the trouble object.
Hi Giuseppe, the client is running version 11.20 SR7 (built 12451).
I actually already tried to rebuild, to some extent, the document and I noticed that, excluding tables from the page layout leads to some improvements: at least the combo-chart on top of the first tab of the main container is finally rendered, even though it takes way more time than how long it take to render the while page (chart + tables) in other browsers.
I actually also played with Browser Mode and Document Mode of IE Developer Tools and is seems like performance is much better in Quirks mode, but the layout is not rendered as it should (especially the QlikView tollbar). Don't know if it helps...
I would assumen sharing a the sample QVW is not a option, so I would suggest to get to Qlik Support for further assistance, you can shared the QVW to them ( since they have a privacy agreement with your company). Make sure to provide the following information:
•The relevant QlikView 16-digit license number
•The full QlikView version number (e.g., 9.0.7119)
•Technical details of the host server/machine, including:
- Do you use Qlikview Webserver or IIs?
- Is this a VMware Server?
•Windows operating system
•32bit or 64bit environment
•Number of CPUs and amount of RAM
- Sample QVW and steps to reproduce.
Well, I finally found what's wrong with IE 9. Speaking with Qlik supports, it turned out that IE 9 has some problems in rendering table-related objects such as containers, pivot-tables and so on...
In the document in question, I nest tables and containers inside containers and this seems to be simply too much for IE 9 to handle...
As a consequence, I had to develop a different version in which containers are simulated by means of buttons, variables and conditioning objects' visibility.
Hope it helps