Yeah, that's an optimistic approach to resolving LO join issues in Crystal.
Once you place criteria on the child table, you've overridden the LO join with the condition specified, they are conflicting requirements.
When specifying a LO join, you request where field = field or the child table field is null, then you add criteria which states that the child must be a set value, so the database logically decides that you're on crack because it can't be both NULL and have a value.
This is an age old misunderstanding of how a LO join works, and Ido is correct in that you can resolve this using a ISNULL check in the SQL, but a Crystal record selection isn't SQL.
In CR8 you are limited in how you can address this, you can might create a database object to address this.
Since you didn't bother to post your database type, and given your understanding of a LO join, I'll guess that you don't have rights to create database objects and resolve this in SQL within a View or a Stored Procedure. It's true that we might edit the SQL generated by Crystal to do this, but I think it will prove even more problematic to attempt it, it's finicky and you need to understand the SQL of the database very well.
A quick database side solution is to create a View of:
select * from SLANLHDR.ANALYSIS_HEADER where SLANLHDR.ANALYSIS_HEADER = "CLIENT TYPE"
Then left outer join your parent table to that.
So the best solution for you will be either to use conditional suppression for the child table criteria or a subreport for the child table, and link via the field.
I'll demonstrate the first as the second will likely be much slower.
Remove the {SLANLHDR.ANALYSIS_HEADER} = "CLIENT TYPE" from the record selection criteria.
Right click the details and select format section->X2 next to suppress and use:
{SLANLHDR.ANALYSIS_HEADER} <> "CLIENT TYPE"
The problem with this approach is that the non Client Type rows are still in the report, so if you perform aggregates, they will have to be conditional.
An example would be using a Running Totals, and in the evaluate->use a formula you'll nee to specify:
{SLANLHDR.ANALYSIS_HEADER} = "CLIENT TYPE"
-k