Report Design: distincount without empty records

I prefer the RT process so her is that version

Name=DC_of_Field1 (or whatever)

Field to summarize=Field1

evaluate= use a formula

reset=on change of group (group1)

place in group1 footer (or details to see row level incrimental changes)

i also found another solution by google:

If you want to know how many records meet a criteria, you use an If-Then-Else formula as described in formula 10 and sum the formula.

However, if you need to do a distinct count of a field in these records, you run into a problem. The records that don't meet the criteria have an else value that also gets counted. The result is that your distinct count is usually one higher than it should be. Some CR users assume that if they simply skip the else line of the formula, that CR will use a NULL value as the else, and then the NULL wouldn't be counted. However, CR does not use an else of NULL by default. It will use the default value for the data type of the THEN value. That usually means and empty string value ("") or a zero for numerics. But here is a way to fool CR into returning a NULL value as your ELSE value:

1) Create a formula called @null and save it without any contents

2) Create an if-then-else formula:

                         if {criteria.field} = "X"   //whatever your criteria is
                         then {table.ID}            //the field you are distinct counting
                         else {@null}               // the formula field you created above
                                      // if your THEN field is a number use Val ({@null}) or ToNumber ({@null}) as your ELSE

3) Do distinct counts of the if-then-else formula.

in your case i have to put it in the group footer.

in this case i can put it also in the group header.

thanks for your help.

When you insert a subreport you can right click on it and select the 'change subreport links'

A box opens which allows you to select the data element(s) fromt he main report and how you want to link it to the subreport.

Just keep in mind that the value used when passing is based on the value that exsits for that line/section in the main report.

You can also pass values back and forth using shared variables. Just keep in mind that the values has to be created and then passed on so if you are taking a value from a subreport back to the main report the shared variable int hemain report must be placed below the section that the subreport is in.

also suppressed subreports do not run so no shared variable can be passed. Tere are tricks around it if you need it.

A new world of reporting is opened for me.

I am starting a new topic about sub-reports.