I keep getting the following error when I insert an outer join either in the
universe or the SQL itself. Can someone explain what this means?
“The table ‘dbo.au_lead’ is an inner member of an outer-join clause. This is
not allowed if the table also participates in a regular join clause. :303”
Listserv Archives (BOB member since 2002-06-25)
Michelle -
I have had this problem before. It is related to how your tables are joined
in the universe. For example, I had a log table with two separate joins to
a userid table - one for the id of the person who entered the log entry, and
one for the id of the investigator. The entry user id was an inner join
because there would always be one of those. The investigator userid was an
outer join because there may or may not be one of those. Therefore, the
userid table was part of an inner join and outer join.
My workaround was to create a view with the inner/outer joins and use the
view in the universe. That seemed to work fine.
By the way - I only got this problem with SQL Server - I also use this
universe against an Oracle database and had no problems.
I hope this helps.
Marian Cooney
McKessonHBOC
Malvern, PA
Listserv Archives (BOB member since 2002-06-25)
Can someone explain what this means?
“The table ‘dbo.au_lead’ is an inner member of an
outer-join clause. This is
not allowed if the table also participates in a
regular join clause. :303”
Some databases do not allow a table to participate in
both an inner and an outer join within the same query,
in particular when the table is in the outer part of the
join. For instance, in Sybase, the following was not
allowed in the past:
A.x = B.x AND A.y *= C.y
I am not sure about the most recent version of Sybase.
Check in Designer. One of your tables probably has an
outer join and inner join, and your BOb document request
is probably using all three tables (both joins).
Randy Coates
Actium @ modis solutions
rcoates@actium.com
Listserv Archives (BOB member since 2002-06-25)