I created several modules within Microsoft Access that run within the Access window “Microsoft Visual Basic for Applications”. Each module consists of a series of about 30-80 SQL queries stored within my Access database, to operate on tables stored within my Access database stored on my hard drive. All the modules ran just fine last week, but two of them started throwing this error yesterday, and I don’t recall making any changes. When I try the debugger, depending on the run, it varies which queries it takes me to, e.g. it originally landed on the first query, now it no longer lands on that one but on some later ones instead, so it seems arbitrary which queries it complains about. All of the queries seem to run just fine when executed manually, outside of the window “Microsoft Visual Basic for Applications”, so no syntax issues. Any ideas what went wrong?

I looked at Run-time error ‘3061’. Too few parameters. Expected 1. (Access 2007), and none of these issues seem to apply to my queries.screenshot. Here’s an example of one of the queries that originally seemed to trigger this error, but no longer does in spite of no changes, since it seems arbitrary where the debugger lands:
Query titled “nulling TB-r public fields”:
UPDATE [current Regionals] SET [current Regionals].[TB-r_public] = Null, [current Regionals].[TB-r_s_public] = Null, [current Regionals].[TB-r_com_public] = Null;