Using Groups in Reports

[shelleyl868]

I am trying to use grouping to avoid displaying information in a report that is duplicated in the rows of my table. Each row of the table also contains unique information, but the duplicated information must be in every row for reasons that aren't important here.



I thought that I could create a group and put these fields in that header and it would only display that information in the row for that group header, but it's displaying it on every row. Is there any way to accomplish this within a report?

I know there are all kinds of problems with this design that could be solved by creating and linking tables. However, this is not possible because my data source is an Excel spreadsheet (linked in my database) that members of my team update, and they do not have Access. I'm basically using Access for reports based on the Excel spreadsheet.

Thanks for your help!

[isladogs]

Its not totally clear why you are seeing repetition
If field A is in the group header and the other fields are not, field A should appear once at the top of the records for that group

A similar result is obtained if you place the field in the detail section and set the field properties to Hide Duplicates = Yes

Either of these should achieve what you want
If that doesn't help, please post 2 screenshots of your report, design view & print preview

[Bulzie]

Are you saying the whole row of data is duplicated or various fields in a single row are duplicated? And as Ridders52 asked, can you provide screenshots of the report or post an example of what it issue looks like.

[orange]

I agree with comments by ridders and bulzie. However, I am wondering why there is duplication in the "table" being used in Access. You seem to have reasons/rationale and I'm not trying to dissuade your approach. My thought is could you have a query to get only the data you need from the spreadsheet and set up your table
with "the better design" and "remove some of the problems".

[June7]

Have you considered installing Access Runtime (it's free) on each user machine so they can run Access file for data input and report output? Then you can eliminate the Excel component. Be sure to split the db for multi-user application.