As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I have a few questions on list boxes in launch pages
1. How do chained list boxes in launch pages get populated? I know they are the result of WHERE statements in the focexec, but how does WebFOCUS retrieve the values? Does it create a hold file for each list box?
2. When the "ALL" option is used in all 4, the browser chokes. How can we get around this?
3. If you have 4 chained list boxes, how can you use in the focexec the selection from only the 4th list box, rather than having it use all 4 WHERE statements that generated the list boxes?
4. Why are the values of some list boxes sorted and some aren't? Is this based on the segtype?
Thank you,
JohnThis message has been edited. Last edited by: Kerry,
WF 7.7.03, Windows 7, HTML, Excel, PDF
Posts: 225 | Location: San Francisco Bay Area, California | Registered: October 26, 2006
1. When you load the web page, WebFOCUS generates an SQL statement under the covers to retrieve the data for the list boxes. Chained boxes will cause that SQL to contain a WHERE. You can use a focexec to populate the boxes instead of the default.
2. You are probably retrieving too much data. Do a COUNT * on your data with no WHERE clauses to see how many potential rows you are trying to bring back.
3. See Tony's answer. Think Dialogue Manager.
4. See Tony's answer. Using a focexec to populate the dropdown boxes will cure a lot of ailments.