In all cases, users are set up withMicrosoft Windows XP, Office (XP, I think), and the latest version ofInternet Explorer. Each page (the .mht file) merely links to the"single-fileWeb page", created from an Excel pivot table, which is connected to anAnalysis Server cube. Most users have the same configuration forWindows Firewall, anti-virus software, spyware protection, and networkconnectivity.
Some users (actually, about one-third) are unable to open the pivottables. In some cases, the screen will "flash" a small icon where thepivot table should be, and then sit there with no hint that anything iswrong. In other cases, the user will get a "frame" of the pivot table(the toolbar and data areas), but no data and no helpful feedback.Allusersare reporting an unexpected behavior; with each change of the pivottable, the display "creeps" up and left slightly: After about twentyclicks on the table, the left margin of the table is off the screen.Has anyone seen this? How can I keep the table from creeping away?
I have the impression that there's a better way to do this. Should I beplacing an OWC object on a page, then populating it? How can Itroubleshoot the failure-to-display problem? I'm writing C# code inVisual Studio .NET v1.1.4322 SP1.
Rick
RickInMesa--
Regarding this...
RickInMesa wrote:
...Some users (actually, about one-third) are unable to open the pivot tables. In some cases, the screen will "flash" a small icon where the pivot table should be, and then sit there with no hint that anything is wrong. In other cases, the user will get a "frame" of the pivot table (the toolbar and data areas), but no data and no helpful feedback.Allusers are reporting an unexpected behavior; with each change of the pivot table, the display "creeps" up and left slightly: After about twenty clicks on the table, the left margin of the table is off the screen... How can I troubleshoot the failure-to-display problem?...
...I can say that in my experience using (MSOffice + InternetExplorer) solutions, it is absolutely necessary to make sure each and every machine running the application must have the exact same version of Office and every machine has been fully patched with all available updates from the Microsoft Update site,http://update.microsoft.com/ .
I know this is a simplistic and somewhat brute-force approach; but, I have found it is the only way to get to ground-zero and then to begin debugging.
HTH.
Thank you, Mark. That's a good tip, and something that needs to be done first, I agree.
What about the "creepy" display? It shouldn't creep away on everyrefresh, should it? Users are saying that they like the pivot table,but just when they get the displayperfect, it's too far offthe left edge of the screen to see the column there. They have to startover, and try to do it with 15 clicks instead of 30.
Rick
RickInMesa--
Regarding this...
...What about the "creepy" display? It shouldn't creep away on every refresh, should it?...
...I am sorry; but, I have no solution for this.
I have seen this sort of thing with embedded components and have reached the conclusion that "some of them work better than others and some of them don't work at all".
IMHO, this is just another piece of evidence that embedded controls in a web application (such as ActiveX, Flash, RealAudio, WindowsMediaPlayer, OfficeControls, the interactive Excel-on-the-web functionality, Crystal, and so on) are out of place, proprietary, and very buggy. For reporting, I like the dynamic reporting approach that offers the enduser some way to build a "query", excecute it, and display the results as HTML or PDF. That's stable. I think that web controls fail because the underlying environment (the browser) is not stable or standardized.
HTH.
Thank you.
0 comments:
Post a Comment