Focal Point Banner


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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
Join Limitations
 Login/Join
 
Member
posted
I am fairly new to webfocus. I was wondering if anyone could help me on how to get around the limitation of 16 active joins. I am working on a report and need to join several oracle tables to get all the data I need.

Thanks!
 
Posts: 26 | Registered: February 25, 2005Report This Post
<Pietro De Santis>
posted
How about getting the DBA to create an Oracle view?
 
Report This Post
<ejaf>
posted
Look in your docucmentation for 'CLUSTER JOINS', they're very efficient and save you coding joins each time you require them.

Basically, you create a new master file which in turn references many tables. An access file is created and this describes the relationships between the tables (ie the join characteristics).

One gotcha to watch out for, when you map a table to another table the cluster join tool creates a relationship with a default one-2-many relationship, right-clicking than make the join a one-2-one.

I have many clients using cluster joins and without exception they are happy and agree it makes their lives much easier once the initial pseudo structure is set-up. (plus it's easier to do it yourself than ask a DBA to set-up a view)

Good luck, happy coding, don't hesitate to ask more if you need to.

P.
 
Report This Post
Guru
posted Hide Post
You could just do a SQL pass-through.
 
Posts: 406 | Location: Canada | Registered: May 31, 2004Report This Post
Master
posted Hide Post
ejaf has the right answer it allows you to create a new master file that will join up to 64 tables together. It better than a DBMS view because it only joins the necessary table to fulfill the request. It also makes it better for UAS user and Administrators that create and use Reporting Objects.
 
Posts: 865 | Registered: May 24, 2004Report This Post
<Pietro De Santis>
posted
EJAF,

Cluster Joins are a great idea.

You just have to be careful that when the table changes in the DBMS, the change has to reflect in the Cluster Join Master.

Thanks for the information.

Pietro.
 
Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders