Access wont save the modification in the queries

A report's RecordSource property can be the name of a table, the name of a saved querydef object, or the SQL statement for an unsaved query.  If you edit data in a table the changes will be reflected in a query, and consequently a report, whether that is the table name, a saved querydef object or an SQL statement as the report's RecordSource property. 

If you edit data in a saved querydef object opened independently of a report, the changes will be saved automatically as you navigate from row to row, and when you close the datasheet.  They will then be reflected in the report's results. 

If you change the definition of a saved querydef object independently of the report or when opened within report in design view, e.g. by changing the criteria by which the query's result table is restricted, or by changing its WHERE clause in SQL view, then you must save the querydef object for those changes to be stored in the query definition.  They will then be reflected in the report's results. 

If the report's RecordSource property is an SQL statement.  You can edit it in the report in design view, either directly in the report's properties, or in query design view or SQL view opened from the properties sheet.  If you do this you will be prompted to save the changes when you close the query design window or SQL window.  You will also be prompted to save the report when you close it.  You should answer yes in each case.

That sounds frustrating.

To help you resolve the problem, though, we need additional details about what you are doing.

What does it mean to say that you "put some requirement into the query"? Where and how do you do that? What is the kind of requirement?

How are you trying to save the query?

Unfortunately, there's more than one way to do most things in Access. We need to know specifically what your steps are.

Thanks for providing enough specific detail to attempt to offer ideas.

Hi @Grerick

Thank you for reaching out to Microsoft Q&A Forum.  

I understand this might be confusing. From what you've described, it looks like the issue is likely related to how Access handles query changes and how reports connect to those queries. 

I also tested this on my end. After adding a new filter to the query and saving it, the report showed the updated results as expected. 

In Access, when you add a requirement or filter to a query, it’s a good idea to ensure the query is saved before using it in a report. If the changes are saved, the report will typically reflect the updated results the next time it’s opened. 

Also, if the report is still showing all records, it could be that the report’s Record Source is still pointing to the original table rather than the query. You can check this by opening the report in Design View and verifying the Record Source property. 

Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution. 

I hope this helps. If the issue still persists, or if I’ve misunderstood any part of your question, feel free to let me know. 

If possible, it would also help to share more details about where and how you're adding the condition to the query, so we can better understand whether the behavior you're seeing is expected.

If the answer is partially 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.