A bit kludgy but I could create say 10 empty tables, same design as production table, on the archive database. I think the archive db can hold about 10 years worth of records. I'll name these tables Archive2021, Archive202, etc. On the production db, I'll set up a select/append query that will ask for the year. The query selects all records for that year and appends them to an empty table, say 'Archive_Temp'. The user is then instructed to open the archive db and Import the 'Archive_Temp' table from the production db into the correct 'Archiveyyyy' table.How about, instead of messing about with tables and queries and naming and renaming, you simply make a back up copy of the accdb and call it the "archive" for the previous year? Then in the currently active accdb, you can delete records not intended for current use going forward.
Not critical but is there a way, via table design, to prevent import into wrong table based on field 'Year_Month' value?
That would do me for 10 years.