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 Widget Model W123 that is made up of SubWidgets. Each SubWidget may have multiple model numbers. Take a look at the table below. Widget Model W123 has two different SubWidget Type AA model numbers. Notice that the total number of SubWidget Type AA units is the same as the total number of Widget Model W123 units.
The second table represents a similar relationship between Widget Model W123 and SubWidget Type BB. The difference here is that SubWidget Type BB has three model numbers instead of two. Also notice that the total number of SubWidget Type BB units is the same as the total number of Widget Model W123 units.
Reporting against these relationships is fairly simple if you only want to show one Widget to SubWidget relationship at a time. My question is this – if you wanted to report both of the relationships shown below in the same report how would you go about doing it?
The data is stored in three tables. The Widget table is joined to the SubWidgetAA table via a one-to-many PK/FK relationship. The Widget Table is also joined to the SubWidgetBB table via a one-to-many PK/FK relationship.
SORRY FOR THE UGLY LAYOUT BELOW. TRIED TO PASTE HTML FROM ANOTHER AUTHORING TOOL.
Widget_Model
Widget_Units
Sub_Widget_Type
Sub_Widget_Model
Installation_Percentage
Sub_Widget_Units
W123
100
AA
SW987
25
25
SW654
75
75
TOTAL
100
100
100
Widget_Model
Widget_Units
Sub_Widget_Type
Sub_Widget_Model
Installation_Percentage
Sub_Widget_Units
W123
100
BB
SWABC
20
20
SWDEF
30
30
SWGHI
50
50
TOTAL
100
100
100
This message has been edited. Last edited by: Kerry,
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007
I would use TAGs in the JOIN command to differentiate between the sub-fields in the 2 different paths. Then, ideally, MORE should be used. However, MORE demands that the fields have the SAME names, which is contradictory. So you are left with using 2 TABLE requests and HOLDing in the same file with a FILEDEF and APPEND.
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006