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've recently found out that one of my reports has spacing between some entries due to data from my SQL joins and even though this data is not displayed, it gives me a big gap in the report.
This report lists our bibliography documents and each document has a copy level, and within each copy level a piece level. I am searching for something in the piece level (a piece type, ie books, cd, etc). I have found the best way to do that is keeping it simple through a join. The report has an option to show the piece level data or not, and has a GOTO that bypasses the pieces level SQL join if that data is not shown. However, I thought I could add an exception to the goto, so that if a user searched on a piece type, the join would be included but the piece level data would not be shown in the report. It's not shown. Instead I get blanks depending on how many pieces each copy has. If there's 20+ pieces, I get a huge gap. If there's 1, nothing.
So it appears joining the piece level data in the SQL gets produced into the report even though it's not visible. So how do I get rid of the gap but retain the data from the join in the search?
Thanks!This message has been edited. Last edited by: Kerry,
I think we would have to get a notion of what the report looks like (in terms of code and in terms of data) before being able to give some advice. It may be as easy as changing PRINT to SUM, but it may be a lot more complicated than that.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007