I wasn't able to convert the database after inserting a space before GROUP BY.Well, this is interesting...
First I checked all the macros as that seemed easiest. When I tried to view queries in design view it wouldn't let me, not that I would have wanted to search every one for a single word. More on that in a moment. Then I tried to output the recordsource of the queries to the documenter and it wouldn't let me because the version was too old.
So I wrote a sub in another db to connect to your db and delve into the sql of each of the queries and look for "description " and it found none. Then I modified the search to find "description" and it found lots. I copied and pasted all into a Word document and did a search for "description" and it stopped at every "description_perte" except there was one that looked like
So why didn't Word or my code find that instance of "description"? Because it is not - it is "descriptionGROUPBY" with a line wrap in between. I'm surprised this query runs at all because I do not think that Access 2016 would let that slip by, but perhaps that is only true for vba code and not Access sql. If I could alter the design and save it, I would open that query in sql view, insert a space before GROUP BY and test it but I am not allowed to edit the design. You will have to try that.VBA Code:
....[T-code_perte_temps_emballage].description GROUP BY...