Backgound:
App opens to a frameset; left frame is an outline, right frame an image
User clicks outline entry to select a PN from a list via @Picklist.
The view used by the PickList is categorized on PN and defined to open collapsed.
The view includes no code in any of the events.
Once the user picks a PN, a 'dashboard' style form (*) opens for the user.
On this dashboard form is a hotspot that allows the user to pick a new PN and update the dashboard form. This hotspot uses the same code as the outline entry.
The use can also exit the dashboard form, return to the frameset and use the outline entry again for a new PN.
The Problem.
The first time the user clicks the outline entry, the displayed picklist view is collapsed.
If they use the dashboard hotspot or reuse the outline entry, the view displayed in the picklist is 100% expanded.
If the user exists the db and reopens it, the first use of the outline has a collapsed view again.
Additional information:
The design of the PN view hasn't changed since 2008.
The dashboard form was last updated 31.Mar.2011 but only to add a new embedded view, nothing about the hotspot was modified. The embedded view is not the one used by the outline entry and hotspot.
Right before this problem started, I had an issue with two of the docs in the PN view that caused a dblookup failure if the PN associated with these two docs was selected. The problem resolved by doing and edit/change content/save/edit/change content back/save again on these two doc.
http://www-10.lotus.com/ldd/nd6forum.nsf/ShowMyTopicsAllFlatweb/2b9974f52302d6a48525786f004563ed?OpenDocument
The PN view includes about 23,000 docs, not sure on the number of categories but less than 23K.
If I try and add in a ViewCollapseAll to the view postOpen event, this spawns an error in the PickList (command not allowed kind of thing).
Here's the code in question - no magic at all here:
PN := @PickList([Custom] : [Single];"";"vwByPN";"Title";"Prompt";1);
luPDesc := @DbLookup("";"";"vwByPN";PN;2);
PDesc :=@Unique(luPDesc);
The problem isn't critical but it's confusing and annoys the heck out of the system users.
Any ideas? TIA for your thoughts.
Doug