Totally, it actually simplifies it.
So you have your query created "querywhatever"
You now create a function in VBA (a sub should work, but for some reason I got less issues when it's a function).
In there you create a few variables.
today(string) = date()
FilePath (string) = The filepath you'll save the file to on the shared drive, including the final ""
Filename = Filepath & "What you want the file called-" & today & ".xlsx"
Then you execute a do.cmd
DoCmd.TransferSpreadsheet acExport, acSpreadsheetTypeExcel12Xml, "queryWhatever", FileName, True
It can help to wrap it with a "DoCmd.SetWarnings False" in case there's some error fields in the extracts but you should really validate the query ahead of time to make sure either those errors are OK or it's error free.
And probably have it set to Application.Close when done
Then you create a macro to run the function (you can use the macro builder)
Then make a batch file and put it somewhere simple (usually root of C: is a good spot)
Then the batch file is just a text file with a string in it like:
"C:\Program Files\Microsoft Office\root\Office16\MSACCESS.EXE" "C:\Users\username\Documents\YOURDATABASE.accdb" /X NAMEOFYOURMACRO
And task scheduler you can search for in the start menu, it's pretty straightforward to schedule the task to run a .bat file, so however often you have the task scheduled to run, it opens your batch file, which opens access and executes your VBA that runs the query and saves it as an excel file in the designated directory, bam, one less thing to do every day.