RunTime Error 3061 - Access Developer Network


	Back to Access Developer Network Comments List

Upload Images @Reply Bookmark Link Email Next Unseen

RunTime Error 3061

Ashlyn Talley

4 years ago

Hello, thought Ive been doing pretty good using the Query Designer to help with my SQL statements but Im finding myself humbled with this one. Im trying to return a record set using similar if not far less complex criteria than I have before in this project but it seems I cannot get past this nagging error.
PatientID (primary key/integer)
Subroutine: cmdPDF_Click

Seems when I use the below statement, hardcoding a PatientID value (402), Im error free.

Set rs3 = db.OpenRecordset("SELECT TOP 6 SchedulingT.*, SchedulingT.HasBeenInvoiced " & _
    " FROM SchedulingT " & _
    " WHERE (((SchedulingT.PatientID) = 402) And ((SchedulingT.HasBeenInvoiced) = False))" & _
    " ORDER BY SchedulingT.DateTime DESC;", dbOpenDynaset, dbSeeChanges)
*******************************************************************************
But when having the PatientID referenced from an open form I receive a continuing error code 3061 & message of Too few parameters. Expected 1

Set rs3 = db.OpenRecordset("SELECT TOP 6 SchedulingT.*, SchedulingT.HasBeenInvoiced " & _
    " FROM SchedulingT " & _
    " WHERE (((SchedulingT.PatientID) = [Forms]![PatientF]![PatientID]) And ((SchedulingT.HasBeenInvoiced) = False))" & _
    " ORDER BY SchedulingT.DateTime DESC;", dbOpenDynaset, dbSeeChanges)

As mentioned, I have used very similar SQL statements to open Recordsets from this same table, seems I may have seen this error before but forgot how to resolve. Thanks

	Ashlyn Talley OP @Reply 4 years ago

	Kevin Robertson @Reply 4 years ago
Try this: `Set rs3 = db.OpenRecordset("SELECT TOP 6 SchedulingT.*, SchedulingT.HasBeenInvoiced " & _ " FROM SchedulingT " & _ " WHERE (((SchedulingT.PatientID) =" & [Forms]![PatientF]![PatientID] & ") And ((SchedulingT.HasBeenInvoiced) = False))" & _ " ORDER BY SchedulingT.DateTime DESC;", dbOpenDynaset, dbSeeChanges)`

	Ashlyn Talley OP @Reply 4 years ago
Thank you much Kevin, that was absolutely spot on, no longer receiving an error and the recordset is performing as expected. Of course couldn't help but know the error had to do with concatenating (SchedulingT.PatientID) and referencing the open form. Looking at how you worked it seems an easy fix. I think of course made it harder than need be. Thanks again!

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Access Developer Network.

Next Unseen

New Feature: Comment Live View