How are duplicates suppressed?

We have a report that is supressing duplicates but I don't see how it is
doing that. So I am not asking how to suppress duplicates; I want to
understand how this report is doing that.

The report is based on a table. The report shows items and their components.
Many components have sub-components but that is not relevant here, except
that the components are shown as a group header. It is only the components
that do not have sub-components that have duplicates. Although there are
duplicate records, there is only one line on the report shown. Is the fact
that the lines are a group header that causes duplicates to be suppressed?

I have looked for obvious answers; the "Hide Duplicates" property is always
"No" wherever I find it in the report. There is not code for the report; in
other words, no event procedures. The quantity shown in the report is the
quantity from a single record; it is not an accumulation or whatever of
multiple records.

The main reason I need to understand how the duplicates is suppressed is
because I need to use the table the report uses and the duplicates cause me
to be suspicious of the data. I want to uderstand the data as much as
possible; I prefer to not have any more surprises.

"Sam Hobbs" wrote in message
...
We have a report that is supressing duplicates but I don't see how it is
doing that. So I am not asking how to suppress duplicates; I want to
understand how this report is doing that.

The report is based on a table. The report shows items and their components.
Many components have sub-components but that is not relevant here, except
that the components are shown as a group header. It is only the components
that do not have sub-components that have duplicates. Although there are
duplicate records, there is only one line on the report shown. Is the fact
that the lines are a group header that causes duplicates to be suppressed?

Yes, that is what report grouping is all about. The group header and footer are
used to aggregate the data that has a common value for the field or fields being
grouped on so those sections only repeat once for all rows having the same group
data.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Thank you, that makes sense when I think about it. I was surprised there is
not a count or summary, but of course that typically occurs in a footer, not
a header. I suppose I just overreacted to encountering duplicate records I
did not expect.


"Rick Brandt" wrote in message
...

Yes, that is what report grouping is all about. The group header and
footer are
used to aggregate the data that has a common value for the field or fields
being
grouped on so those sections only repeat once for all rows having the same
group
data.

"Sam Hobbs" wrote in message
...
Thank you, that makes sense when I think about it. I was surprised there is
not a count or summary, but of course that typically occurs in a footer, not
a header. I suppose I just overreacted to encountering duplicate records I
did not expect.

Well in a group header/footer grouped on the field [ID] you will see one
instance of each value if you use a ControlSource of...

[ID]

....If you use a ControlSource of...

=Count([ID])

....you will get the count of rows having each particular ID value. Sum([ID])
would give you the sum, etc..


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com