Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Changing left outer join to inner join

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] Changing left outer join to inner join
 Login/Join
 
sosterle
Gold member
posted
Hi everyone -

I saw a posting from Feb 2009 regarding the error message that I'm now getting on a left outer join, but as I got to the bottom of the discussion that was listed as "solved", it doesn't appear that a solution was reached.

I've got two regular master files that I wrote a procedure against sometime ago. I created a left outer join from two fields in one master file to the same two fields in the second master file. It worked fine.

The developer who uses this report recently told me that it started giving the following error about two months ago:

(FOC32456) ANSI-COMPLIANCE ENFORCED BY CHANGING OUTER JOIN TO INNER
0 NUMBER OF RECORDS IN TABLE= 0 LINES= 0

It used to work before but now it's giving this error. There aren't any hold files, just two regular master files.

Anyone run into this and find a solution? I've searched through Tech Support and the Join topics and, unless it's sailing over the top of my head, I'm missing a solution.

Much thanks!
Shel

This message has been edited. Last edited by: sosterle,


PROD: WebFocus 7.6.9 on WinXP
 
Posts: 59 | Registered: October 31, 2006Report This Post
sosterle
Gold member
posted Hide Post
Don't know if this will help anyone else who might encounter this problem, but this worked with our situation.

I doubled check the actual data that was in the fields being joined and, somehow, the SQL script that updates the master file dropped one of the join fields and the values for the field were all NULL. Once I brought it to our DBA's attention, he re-inserted the field in the script, re-ran it and the report runs fine now.

So if you've got a procedure with a left outer join on two regular master files and you get an ANSI-COMPLIANCE error that says it's changing the outer join to an inner join, you might try checking the data in the joined fields to see if there's something abnormal there.

Just a suggestion!


PROD: WebFocus 7.6.9 on WinXP
 
Posts: 59 | Registered: October 31, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Changing left outer join to inner join

Copyright © 1996-2020 Information Builders