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.
JOIN
FILE TEST_FACT_ONE
AT TEST_FACT_ONE.TEST_FACT_ONE.BUS_DTE TO MULTIPLE
FILE TEST_DIM_CALENDAR AT TEST_DIM_CALENDAR.TEST_DIM_CALENDAR.BUS_DTE
TAG J0 AS J0
WHERE TEST_FACT_ONE.TEST_FACT_ONE.BUS_DTE EQ J0.TEST_DIM_CALENDAR.BUS_DTE;
END
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
JOIN LEFT_OUTER field1 IN FILE1 TO MULTIPLE field2 IN FILE2 TAG J0 AS J0 WHERE field3 NE -1 ; END
It seems to me that you combined 2 different syntaxes: "JOIN field IN file" does NOT support WHERE clauses. "JOIN FILE file AT field" allows WHERE clauses. See wf77crlang.pdf pages 827 - 847. Probably WF 7.7 was lenient...
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
...and that's what you get for introducing two different syntaxes for the same thing...
I never understood why conditional joins had to have a different syntax. The only thing it seems to add is confusion.
I say: get rid of the conditional join syntax and add WHERE-clause syntax to regular joins. That cleans up the generated SQL too (why use implicit join syntax at all?).
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :