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 am attempting to code selection criteria that looks like this --
Table File ABC Sum MAX.EFFECTIVE_START_ID Print . . .
(WHERE TOTAL MAX.EFFECTIVE_START_ID EQ EFFECTIVE_START_ID AND PRORATION_STATUS EQ 'L') OR DIM_PERSON.EFFECTIVE_END_ID EQ MISSING
Focus is displeased. Does anyone know how I should talk nice to Focus to get it to digest this logic?This message has been edited. Last edited by: Kerry,
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
I understood what he said, but it just changes the error --
0 ERROR AT OR NEAR LINE 15 IN PROCEDURE ADHOCRQ FOCEXEC * (FOC258) FIELDNAME OR COMPUTATIONAL ELEMENT NOT RECOGNIZED: TOTAL BYPASSING TO END OF COMMAND (FOC009) INCOMPLETE REQUEST STATEMENT
It appears that the WHERE must be up against the TOTAL in order for the parser to figure it out.
It may be that the internal matrix isn't pleased with a WHERE TOTAL and a WHERE being put in the same logic. That would be disappointing.
J.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
What happened was that you were mixing two very different WHERE statements: 1. WHERE ... 2. WHERE TOTAL ... They must be separate: WHERE acts on input records WHERE TOTAL acts on output lines
Jack's syntax effectively did that.
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