Microsoft Access Duplicating Report

Question

I have a report made up of sub queries that creates what seems like at least 12 duplicates of itself. This is attached to the actual report and I have no way of deleting them without it deleting the original copy that I need. They seem to be linked in someway but I am not sure how. How do I stop this from happening? I did not originally create this report and I tend to have trouble opening it because of the amount of copies. Is there any way to put some sort of break in the footer to have this stop? I can not share a screenshot due to the information on the form but if anyone has had a similar problem and could share some insight that would be lovely.

Answer 1

Dear @Rachel,

Welcome to Microsoft Q&A Forum!

Based on your description, I can see that this happens in Microsoft Access when the report’s underlying data returns more than one matching record. Access may not actually duplicate your report object, it simply prints the report once for every row returned by the report’s Record Source or subreports. That’s why you’re seeing 12 copies, your main query or one of the subqueries is returning 12 rows, so Access repeats the report 12 times.

There are several reasons that may cause it:

Access repeats a report when:

1.The main Record Source joins to another table/query that has multiple matching rows

• If a parent record links to 12 child rows, Access produces 12 copies of the report.
• This includes subqueries that are not limited to a single row per parent.

2.A subreport or subquery is placed in the Detail section:

• Items in the Detail section repeat once per related row.
• If a subreport returns 12 rows, the main report prints 12 times.

3.Joins are missing or incorrect, causing a Cartesian join: missing primary‑key relationships can multiply rows unexpectedly.

You can do these steps to confirm it: open the Record Source of the main report directly (open it as a query). If you see 12 rows instead of 1, the report is behaving correctly, it’s showing one report per returned row.

Therefore, I have tried my best to find these ideas that you can try to see if they can help:

1.Ensure each subquery returns only one row per parent: use one of SELECT DISTINCT ... or GROUP BY ... or apply criteria that limits results to a single record.

2.Review your joins to make sure each join uses a key-to-key relationship and does not accidentally create multiple matches.

3.Move subreports out of the Detail section:

Place subreports in:

• the Report Header,
• Page Header, or
• a Group Header

So, they run once per parent record instead of per detail row.

Additionally, I found that many users had similar issue as your case, but there is no official confirmation for a proper fix. However, I also found these articles during my research that may be related to your concern, you can consult them to see if they can give you more insights:

• This case was partially similar to your situation, please kindly check the comments for a potential method provided by a user in there: https://www.access-programmers.co.uk/forums/threads/access-report-creating-duplicates.301160/
• https://www.accessjumpstart.com/hiding-duplicate-records-using-running-totals-over-a-group/
• https://nolongerset.com/hide-dupe-values-in-reports/

Please note that our support is limited to providing guidance based on official Microsoft documentation. Any third-party resources or references shared above are intended solely for informational or consultative purposes. Microsoft does not guarantee the accuracy, reliability, or continued availability of third-party content, and we recommend exercising discretion when referring to such materials. 

I hope this information can help you. Wish you a pleasant day!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 2

To address the issue of duplicated reports in Microsoft Access, it is important to first understand the structure of your report and the queries that are generating these duplicates. Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Review the Queries: Check the subqueries linked to your report. If they are returning duplicate records, you may need to adjust the criteria or use distinct queries to limit the results.
2. Grouping and Sorting: Ensure that your report is properly grouped and sorted. If you have multiple fields grouped, it can lead to duplicates. You might want to experiment with the grouping properties to see if changing them reduces the duplicates.
3. Footer Adjustments: If you want to prevent duplicates from appearing in the footer, consider modifying the footer settings. You can try to remove any calculations or fields that might be causing the report to repeat entries.
4. Testing Changes: Make changes incrementally and test the report after each change to see if the duplicates persist. This will help you identify which adjustment resolves the issue.
5. Backup Your Report: Before making significant changes, ensure you have a backup of your report to avoid losing the original layout and data.

If these steps do not resolve the issue, you may need to consult the Microsoft Access Help documentation for more detailed guidance on report design and troubleshooting.

---

References:

• No current record error when you print or preview a report in Access

Answer 3

The problem is more likely to be due to the report's RecordSource query returning multiple instances of each row, or at least of the set of columns used by the report. Open the query independently of the report and see if multiple instances of each complete row are returned. If so, edit the query's SQL statement so that it starts with SELECT DISTINCT rather than just SELECT. If it returns multiple instances of each row, but with different values in one or more columns not used by the report, then delete those columns from the query's SELECT clause in SQL view (NB: don't do this in query design view, as one or more of the additional columns might also be used in other clauses of the query).

If the report's RecordSource is an SQL statement rather than a saved query, copy the SQL statement to the clipboard, and then paste it into the query designer in SQL view. Do as above, and if the amended SQL statement returns only one instance of each row, copy it and paste the amended statement back into the report's RecordSource property in place of the original statement.