hanchilicious
Programmer
Hello,
I'm using XI on SQL 8.
Basically, I just want to know wtf is going on here...
I am running a report that is based on the following:
selection criteria: not isnull({productmastertable.product})
using two tables linked on keys
grouped by country, sales group, product
data displayed at GF3 level - all other sections suppressed
For the UK, for example, for one customer, I get 5 records. I can confirm this by conditionally suppressing the display section based on {mytable.country} <> 'UK' and conditionally colouring the data with {if {mytable.customer} = '110017' and {mytable.country} <> 'UK' then crlime else crnocolor.
I get 5 coloured rows.
Then I take these two conditions and put them in the selection criteria, so it looks like: not isnull({productmastertable.product}) and {mytable.country} = 'UK' and {mytable.customer} = '110017'
I get 126 rows. 126 are displayed. 126 are coloured.
The second result is correct. Where do the 121 rows go in the first example?
I'm using XI on SQL 8.
Basically, I just want to know wtf is going on here...
I am running a report that is based on the following:
selection criteria: not isnull({productmastertable.product})
using two tables linked on keys
grouped by country, sales group, product
data displayed at GF3 level - all other sections suppressed
For the UK, for example, for one customer, I get 5 records. I can confirm this by conditionally suppressing the display section based on {mytable.country} <> 'UK' and conditionally colouring the data with {if {mytable.customer} = '110017' and {mytable.country} <> 'UK' then crlime else crnocolor.
I get 5 coloured rows.
Then I take these two conditions and put them in the selection criteria, so it looks like: not isnull({productmastertable.product}) and {mytable.country} = 'UK' and {mytable.customer} = '110017'
I get 126 rows. 126 are displayed. 126 are coloured.
The second result is correct. Where do the 121 rows go in the first example?