12-11-2012 10:07 AM
I've come across a problem using Enterprise Guide 4.3 and wondered if there was a fix for it, I wonder if you lovely people may be able to help.
I've got a process that I'm trying to edit to replace one of the base data tables as the table that was being used doesn't contain enough historical data for the report I'm producing. I've used the query builder and swapped out the old table (t1) for the new one (t3). The data types are the same for the fields that I'm using but i'm getting a lot of the error "ERROR: Column t3.CompanyNo was found in more than one table in the same scope." with a lot of the same error for different columns. I've spoken to our resident SAS guru's in our head office but they can only suggest building the report again from scratch (which I'd really rather not do, it took a while to build).
I've attached the code as it's showing with the errors, if anyone could suggest a fix for this it would be fantastic.
12-11-2012 10:25 AM
Thanks for the quick response.
I'm not sure how the link relates to my issue exactly. I'm fine with duplicate records pulling through (I don't believe they should but I can deal with that issue separately), my issue is that the query won't run at all, I simply get the error message above (as seen in the attached log).
I'd more than happily go and look at the code again but my lack of SAS code knowledge is not letting me see how to fix my issue with the link supplied.
04-11-2013 06:53 PM
I recently got this error too on a rather complex set of joins (8 tables).
What fixed it for me was to reset the order of all the joins, especially the left outer joins.
Good luck! You can message me if you have more questions.
08-25-2017 11:11 AM
04-12-2013 11:21 AM
I find the FROM clause a little overwhelming, but one thing I noticed is that after a long series of join, your code contains
"ON (t3.IntermRef = t8.INT_NEW_AG_NO),CORPDIST.QUOTES_ALL_TEMP_RICH t3 LEFT JOIN SMEQUOTE.SME_PROSPECTS t2"
so you're using CORPDIST.QUOTES_ALL_TEMP_RICH as T3 twice in the same query.
Could this be a problem?