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.
We created a data mart (sql table) and accompanying master file. It is quite large (8M+ rows)
The user uses selection dropdowns to extract a portion of the data mart into an Excel spreadsheet output.
At times the user will simply select an unreasonable amount of rows for output..sometimes more than Excel can hold.
Is it possible, based on the number of rows returned by the fex, the throw out a message as to how many rows are returned or better yet if above some threshold we determine, to stop the report from being generated at all?
Something like:
Grab Selection Execute report if number of row returned > 200,000 Pop up a message.."Too much Data" otherwise open the report.
I figure after creating the report, I could create a second report consisten of a simple message and then imbed an IF/ELSE that determines which code to run...based on the number of rows returned...but how do I make a variable or something to capture: RowsReturned?This message has been edited. Last edited by: FP Mod Chuck,
Yes to Martin's 'Notice' as to pay attention to &RECORDS and &LINES. You'll have to 'pre-process' your TABLE FILE to a HOLD FILE to check that value and follow that with a -IF &LINES.EVAL GT 123456 THEN GOTO :TooManyRecords ELSE GOTO :Continue;.
The -:TooManyRecords label / section will need a display message followed by -GOTO :TheEnd.
Or, something along those lines. I did that using a Reporting Object except that I had a WHERE statement that limited the output to 50000 records and set a &Message that was added to a Red Line in the HEADING.
It all depends on how far you want to go with this. The options are limited only by your imagination
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005