You could have a small routine that -once you have reviewed the parameters for each update query, executes these queries one after the other. If there is some criteria that would prevent a query to run , you could trap and give a Message to the user.
If all queries must complete successfully, or no updates should be applied, you will have to consider Transaction Logic.
It isn't clear from your database, what should trigger the execution of any or all update queries.
Here's a recent example from a database I have that runs several routines and a query in succession. The DoEvents line provides a slight interrupt for Access to let the processor do other things.
This all gets started when I click on a label on a form
Code:
Private Sub Label0_Click()
InternetAvailabilityFullProcess
End Sub
And this is the series of actions that gets executed.
Code:
Sub InternetAvailabilityFullProcess()
10 On Error GoTo InternetAvailabilityFullProcess_Error
' make sure you have saved a copy of the Events (UniversalTelemetryClient)
' as a .txt file "C:\users\jack\documents\AllEventsRaw.txt"
'
'Run ImportEventsWithSpec to get txt data into table ALLEventsRaw
'Run the query to get event 55 data
'Run the prepareInternetEventsJED to get proper Date and Time info
'Run the ProcessInternetAvail to get a printout/txt file showing outages
' and durations --file is "c:\users\jack\documents\BellInternetDrops" & Format(Date, "MMMDD") & Format(Time, "_HHAM/PM") & ".txt"
'
20 Debug.Print "starting the import at " & Now
30 CurrentDb.Execute "Delete From AllEventsRaw", dbFailOnError
40 DoEvents
50 ImportEventsWithSpec
60 Debug.Print "Import completed at " & Now
70 DoEvents
80 CurrentDb.Execute "Delete From InternetEventsJED", dbFailOnError
90 Debug.Print "Running query to extract proper Date and time and only Event (55)"
100 DoEvents
110 DoCmd.OpenQuery "qInternetLog"
120 Debug.Print "Query finished at " & Now
130 Debug.Print "Preparing the InternetEventsJED table to remove duplicate/replicate records at " & Now
140 prepareInternetEventsJED
150 DoEvents
160 Debug.Print "Finished preparations at " & Now
170 ProcessInternetAvail
180 Debug.Print " Finished processing outages and duration at " & Now
190 Debug.Print " The file is available at " _
& "c:\users\jack\documents\BellInternetDrops" & Format(Date, "MMMDD") & Format(Time, "_HHAM/PM") & ".txt"
'
200 MsgBox " The file is available at " _
& "c:\users\jack\documents\BellInternetDrops" & Format(Date, "MMMDD") & Format(Time, "_HHAM/PM") & ".txt", vbOKOnly
'
210 On Error GoTo 0
220 Exit Sub
InternetAvailabilityFullProcess_Error:
230 MsgBox "Error " & Err.Number & " (" & Err.Description & ") in procedure InternetAvailabilityFullProcess, line " & Erl & "."
End Sub
Good luck.