Adding New Table to an Existing Report

[CPK6104]

I'm adding a new table (oracle) to an existing report (CR2008) and I get the following error
Failed to Retrieve Data... [ok] Database Connection Error: If tables are already linked then the join type cannot change.

I'm simplay adding a new table to a report that has worked very well for years and I'm letting CR choose the join type. Any ideas? Thanks.

 

[fisheromacse]

as a general rule, i don't let crystal do the joins.

 

[CPK6104]

I've tried letting CR pick the join type and I've tried choosing the join type myself and I get the same results.

 

[Turkbear]

Hi,
If using a Left Outer Join be sure not to apply any selection criteria to the right-hand table - that changes the join type to Equi and maybe your connection/database does not allow that.



To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[CPK6104]

Thanks for the reply. I am using a Left Outer Join on the new table... but I'm not sure I know what you mean when you say "not to apply selection criteria to the right-hand table" (sorry).

 

[fisheromacse]

Turkbear is saying that you cannot have any items from the right hand table in the 'is equal to'/'is one of'/etc in the select expert.

 

[CPK6104]

Got it. Thank you!

 

[Madawc]

You can apply selection to the right-hand table, provided you first test for nulls. When the record is not there, the field value will be null.

Madawc Williams (East Anglia, UK). Using Crystal 11.5 with SQL and Windows XP

 

[lbass]

Madawc, No, that is not necessarily true. Consider this instance:

Table1.Type Table2.Year
A 2011
B
C 1997

If you have a left join FROM Table1 TO Table2, and you want all types to appear, if you add a selection formula like this:

isnull({table.year}) or
{table.year} = 2011

...only types A and B will be returned. Testing for nulls doesn't allow you to pick up those types where there is a non-null value that doesn't meet the criteria.

Ken Hamady discussed this also in his most recent newsletter.

-LB