Elegance should never be underestimated.
Elegant solutions have a habit of working more reliably than bodge-fixes.
Elegant code, reused elsewhere, is less likely to fall over due to its inherent consistency.
The Requery procedure can be used to do what you want but I confess to a little confusion as you refer separately to reports and queries. They are different objects (even though a report will often have a record source of a query).
I would also like to confirm my understanding of exactly what you're trying to achieve here - is it that you want a form and a report both to be active at the same time and that making a change to the selection on the form will update the results shown by the report?
Sorry for the delay...I have been distracted with other problems. To answer your question, yes, but the report doesn't necessarily have to be open at the same time. Rather, when the report is opened, it should have the required data in it. Here is another example.
I have a form "frmEnterTrade" that populates a table "tblTradeInfo". tblTradeInfo forms the source to part of a query, "qryTradeHistory". The qryTradeHistory query is the source to a report, "rptTradeSummary".
From the user's perspective, data is entered into frmEnterTrade, and that data summarised in the rptTradeSummary report.
However, for newly entered data in frmEnterTrade to appear in rptTradeSummary, the qryTradeHistory query must first be updated. The user obviously isn't concerned with the query, only the inputting of data and viewing the final report.
Access doesn't update a query automatically, hence I need to have code to update the query before opening the report. The only way I know how to do this is by opening and then closing the query. This works, but for more complicated table/query combinations this gets quite clunky, hence my wondering if there is a more elegant method. Especially given that this must be a reasonably common need.