title: Why Run-time error '3061'. Too few parameters. Expected 1? Access 2010
body: <p>I have researched all the STACKOVERFLOW questions on this but cannot make it work.  I have a simple table:</p>
  
  <p><img src="https://i.stack.imgur.com/w0QFq.jpg" alt="enter image description here"></p>
  
  <p>And a form:</p>
  
  <p><img src="https://i.stack.imgur.com/tUsSu.jpg" alt="enter image description here"></p>
  
  <p>I want to extract the fields from the table T:ActityRoster and the “Activity Date” from the form and “add” them to a table T:ActivityHistory.</p>
  
  <p><img src="https://i.stack.imgur.com/p2RTT.jpg" alt="enter image description here"></p>
  
  <p>A STACKOVERFLOW expert helped me with some code, but it won’t even set the first recordset:rsIn</p>
  
  <pre class="lang-vb prettyprint-override"><code>Dim ActID As Integer, actDate As Date, val1 As Long, val2 As Long, val3 As Boolean, val4 As Currency
  
  Dim db As Database, rsIn As Recordset, rsOut As Recordset
  
  Dim strSQL As String
  
  Set db = CurrentDb
  
  ActID = Me.cboActivityName.Column(0)
  
  strSQL = "SELECT * FROM T:ActivityRoster WHERE [ActivityID] = ActID"
  
  Debug.Print strSQL
  
  Set rsIn = db.OpenRecordset(strSQL, dbOpenDynaset, dbReadOnly)
  
  rsIn.MoveLast
  
  Set rsOut = db.OpenRecordset("T:AttendanceHistory", dbOpenDynaset, dbEditAdd)
  
  rsOut.MoveLast
  
  actDate = Me.ActivityDate.Value  ' retrive the date from the form
  
  With rsIn
      .MoveFirst
      Do
      val1 = !ActivityID
      val2 = !MemberID
      val3 = !Attended
      val4 = !AmtSpent
  
             With rsOut
                 .AddNew
                 !ActivityDate = actDate
                 !ActivityID = val1
                 !MemberID = val2
                 !Attended = val3
                 !AmtSpent = val4
                 .Update
             End With
  
      .MoveNext
      Loop Until .EOF
      .Close
  
  End With
  
  rsOut.Close
  Set rsIn = Nothing
  Set rsOut = Nothing
  Set db = Nothing
  
  End Sub
  </code></pre>
  
  <p>I have verified that all field names are correct and are consistent data types. When I put the query back into Access, it gives what is expected.  </p>