I had a problem with the 6.0.4 view applet yesterday, and I accidentally “fixed” it… Unfortunately I don’t know why the fix works, and that bugs me…
The end users are using I.E. 6.0.2800 to bring up a “MainFrame” frameset in a one database. When they click on a link in the “Menu” frame of the frameset, it opens up database #2 in the “Main” frame of the frameset to a default view… Pretty simple stuff…
The default view in database #2 is displayed via the Notes view applet. It has 3791 documents categorized into 5 categories. It has 9 columns, one hidden, some dynamically sortable, some with formulae, and some with just field names. (The last two columns are “comments” fields, which can be lengthy…)
Anyway the users can click on each of the twisties to open each of the categories except for the last one. (Click that one, and nothing happens.) Users who open this view in the Notes client do not have the problem.
I tried many things to fix the issue: reloading the page, emptying the browser cache, refreshing the view itself, re-indexing the view itself, making sure all columns in the view had unique numbers on the “advanced” tab, checking the “Reader” fields on the documents in the view against other documents in the view (to see if there were any differences), and ultimately rebooting the server…
What finally fixed the problem was physically adding an additional “blank” column to the far right of the view… Doing this provides some extra “space” behind the comments columns on the right when scrolling in the browser, but it has no other noticeable effect from the users’ standpoint.
At first I was not even sure this accidental addition had fixed the problem, but when I removed the last “blank” column from the view again, the last twistie in the view stopped working again… I can repeat the break/fix cycle over and over.
Any ideas on what the “real” issue is with the view applet, and why adding a blank column to the end of the view fixes this particular twistie problem?