Run the query either within a macro or module. Start either with Set Warnings
off; run the query; then, and this is important, Set Warnings back on.

First I'd design your query so it doesn't append duplicates if at all
possible.   This takes more time and disk IOs to process.   Also I
prefer not to consume needlessly autonumbers but I'm just a neat freak
where possible.

I prefer, if DAO, to use Currentdb.Execute strSQL,dbfailonerror
command instead of docmd.runsql.  For ADO use
CurrentProject.Connection.Execute strCommand, lngRecordsAffected,
adCmdText  

If you're going to use docmd.setwarnings make very sure you put the
True statement in any error handling code as well.   Otherwise weird
things may happen later on especially while you are working on the
app.  For example you will no longer get the "Do you wish to save your
changes" message if you close an object.  This may mean that unwanted
changes, deletions or additions will be saved to your MDB.

Also performance can be significantly different between the two
methods.  One posting stated currentdb.execute took two seconds while
docmd.runsql took eight seconds.  As always YMMV.

Tony