Ms Access 2010 Run-time Error 3061
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the ms access runtime error 3061 too few parameters. expected 1 workings and policies of this site About Us Learn more about run time error 3061 too few parameters expected 2 Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions too few parameters. expected 1 access Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other.
Run Time Error 3061 Too Few Parameters Expected 3
Join them; it only takes a minute: Sign up Run-time error '3061'. Too few parameters. Expected 1. (Access 2007) up vote 5 down vote favorite I have the following 'set recordset' line that I cannot get working. The parameters seem correct according to all available help I can find on the subject. The error displays : "Run-time error '3061'. run time error 3061 too few parameters expected 4 Too few parameters. Expected 1." Here is the line of code: Set rs = dbs.OpenRecordset("SELECT Centre_X, Centre_Y FROM [qry_all_details] WHERE ID = " & siteID & ";", dbOpenSnapshot) Where rs is the recordset (Dim rs As Recordset) and dbs = CurrentDb() Any help would be appreciated. I have tried removing the WHERE cause with no effect, and also using single quotes between double quotes, but no joy. Many thanks. ms-access vba share|improve this question edited Mar 26 '11 at 20:31 gideon 15.1k54893 asked Mar 26 '11 at 20:23 uk52rob 26112 Is this query you're opening a parameterized one? Maybe it's expecting a value... –Tim Williams Mar 26 '11 at 20:35 1 Not sure if it's worth noting but your "one line" of code, at least as you entered it, is occupying two lines. Is that correct or is just the formatting here at SO? –Oneide Mar 26 '11 at 22:55 add a comment| 8 Answers 8 active oldest votes up vote 22 down vote "Run-time error '3061'. Too few parameters. Expec
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 18:57:54 GMT by s_wx1062 (squid/3.5.20)
Ask a Question Need help? Post your question and get tips & solutions from a community of 418,595 IT Pros & https://bytes.com/topic/access/answers/660221-dao-run-time-error-3061-too-few-parameters Developers. It's quick & easy. in DAO: Run time error 3061 Too few parameters.... P: n/a Richard Hollenbeck I wonder what I'm missing? I really feel like a retard because I've been screwing with some code for a very long time. I just must be missing something very simple. In the following example, I've stripped away everything that doesn't cause the too few error to make my question a little simpler. Here's the problem in its simplest form inside a report: Dim db As DAO.Database Dim rs As DAO.RecordSet Set db = CurrentDb Set rs = db.OpenRecordset("SELECT * FROM qryTableOfGrades") 'where qryTableOfGrades is a saved crosstab query. I get "Run time error 3061 Too few parameters. Expected 0." but if I just make that too few parameters last line: Set rs = db.OpenRecordset("qryTableOfGrades") I get "Run time error 3061 Too few parameters. Expected 1." And if I do this: Set rs = db.OpenRecordset(qryTableOfGrades) ' without quotes I get "variable not defined." If I run the query by itself without the report it runs fine. Jun 10 '07 #1 Post Reply Share this Question 1 Reply P: n/a Allen Browne There is a name in qryTableOfGrades that Access cannot resolve to a field name, so it interprets it as a parameter. The parameter could be several things, e.g.: a) Something like this: [Forms].[Form1].[Text22] When you run the query, the Expression Service handles that reference. But the ES is not available in DAO code, so it is treated as an unsupplied parameter. b) A misspelled field name. c) A field name in the Filter or Order By properties of the query, if the field no longer exists. You should be able to identify what the parameter is by closing all forms, running the query, and seeing what name it asks for. It is possible to supply the parameter programmatically, e.