There is such a thing as opening the table with the dates and stepping through the recordset.
The catch with the macro-driven queries is that they might have an issue with that externally defined parameter.
To be honest, I wouldn't do it QUITE that way. But all is not lost. You have the macro. There is an option to convert the macro to VBA. if you did that, you could see how each of your queries is run. You could then convert each query to a PARAMETER query (q.v. in the help files).
So if you build a loop to scan the recordset with the dates, and once for each record in that controlling recordset, run the VBA code you converted, and just supply the value from the controlling recordset as a parameter for each query inside the loop, that would do it for you.
Leaving the macro AS A MACRO will eat your socks for you because of the issues involved with parameter queries in macros.