In BO v5 using a SQL Server database connection, I am unable to create an outer join. The outer join tick boxes are greyed out. Can anyone help please?
Bob
Bob Humphrey (BOB member since 2009-05-13)
What version of SQL Server are you using?
Why not try hardcoding the join, you want, in join properties?
Mak 1 
(BOB member since 2005-01-06)
Thanks, I am using SQL Server 2005.
I tried entering ‘table1’ LEFT OUTER JOIN ‘table2’ ON’‘column a’=‘column b’ in the Join properties but cannot get BO to parse it.
I am more used to Oracle where a simple (+) does the trick.
Bob Humphrey (BOB member since 2009-05-13)
Well, 2005 is unsupported, for version 5 :).
Your ANSI syntax is correct.
Have a look at this post, I discussed this sort of thing, a while ago, it may help:-
https://bobj-board.org/t/59082
Mak 1 (BOB member since 2005-01-06)
Using *= in SQL Server is the same as the (+) in Oracle.
This Microsoft article should help:
http://msdn.microsoft.com/en-us/library/aa213228(SQL.80).aspx
Regards,
Mark
Mark,
This old style - NON ANSI - outer join will only work in certain SQL Server 2005 compatability modes.
Good article here:-
Mak 1 
(BOB member since 2005-01-06)
Well thanks for all the replies. The answer for me is in the join properties to use (for sql server) the asterisk to denote outer join (just as for the (+) in oracle) This revealed a further issue in that it doesn’t accept an outer join on a pair of views which are themselves products of joins.
I’m having to create different views to solve this but the advice is very welcome for future reference.
Bob Humphrey (BOB member since 2009-05-13)
Well thanks for all the replies. The answer for me is in the join properties to use (for sql server) the asterisk to denote outer join (just as for the (+) in oracle) This revealed a further issue in that it doesn’t accept an outer join on a pair of views which are themselves products of joins.
I’m having to create different views to solve this but the advice is very welcome for future reference.
Bob Humphrey (BOB member since 2009-05-13)
Bob,
There is a work around for this - I’ve not used that version of BusinessObjects for a while but there is a solution on here.
Aha, found it:
Regards,
Mark