' If it crashes before it gets here, warnings are not turned back on! One option for suppressing the messages is to SetWarnings False before running the queries, then SetWarnings True after: ' cstrQueryName is a constant with the name of an action queryĭoCmd.RunSQL 'DELETE FROM tblMyTable WHERE Bad = True ' RunSQL and OpenQuery are the simplest to invoke, but they display the previously mentioned warnings, which require user interaction. One may assume all three are equivalent, but the first two should be avoided. Allows you to return the # of rows affected. Does not show messages that require user interaction. Shows messages that require user interaction.Įxecutes either a SQL statement or a saved query. Shows messages that require user interaction. VBA offers the following methods for executing Action queries in code:Įxecutes a SQL statement, not a saved query. When running Action queries in VBA code, you generally do not want to display these messages, since they require a user response before the code can continue. The second displays the number of rows that will be affected: The first is a warning, which asks you to confirm:

When you run Action queries interactively, Access displays two Action queries in Microsoft Access are queries that add, modify, or delete records from tables using INSERT, UPDATE, and DELETEĬommands (or create a new table via MAKE TABLE).

Sql prompt where clause warning