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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
I have a report which I developed in our Dev environment running 8104 and tried to move it over to Production environment which is currently on 8009 and it does not run. It is giving me an error of "(FOC36316) WHERE-BASED JOIN FROM NON-FOCUS TO FOCUS NOT SUPPORTED."
The report runs perfectly fine in Dev. Was there support added after 8009 to allow this Join to function properly or is there some setting that might not be set right in Production? Has anyone else ran into this before? I've verified that the data source it is trying to link to is available in Prod as well.
Here's the bit of code that it seems to be hung up on, which is indeed joining from a SQL table to a FOCUS.
LEFT_OUTER FILE vwloanservcustomertask
AT VWLOANSERVCUSTOMERTASK.VWLOANSERVCUSTOMERTASK.TASKNUMBER TO MULTIPLE
FILE foclossdraftbranchcodes AT FOCLOSSDRAFTBRANCHCODES.SEG01.CIT TAG J4 AS J4
WHERE ( VWLOANSERVCUSTOMERTASK.VWLOANSERVCUSTOMERTASK.TASKNUMBER EQ J4.SEG01.CIT ) AND ( VWLOANSERVCUSTOMERTASK.VWLOANSERVCUSTOMERTASK.SERVICINGBRANCH EQ J4.SEG01.SERVBRANCH );
ThanksThis message has been edited. Last edited by: capples,
WF 184.108.40.206 Windows 10 64bit HTML, AHTML, PDF, Excel
Apparently such a join was not yet supported in your earlier 8.x release.
Solution is to defer the join: omit the JOIN in the table request against the database table (vwloanservcustomertask), HOLD the result in Format Focus (or Xfocus), and then join the held Focus file to foclossdraftbranchcodes.foc.
Note that, by the nature of the data sources, the join you coded would not be passed through to the database server, so postponing the Join to the reporting step makes little difference in execution efficiency.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005