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,

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!