[valerov]

hello everyone. im getting the error: "run time error 3061 - too few parameters. expected 2" when using a select query. i have the following code:

 dt.recordsource="Select * from Table_Name WHERE Field1 like '" & combo1.text & "' AND Field2 like '" & combo2.text & "' AND Field3 like '" & combo3.text & "'"
dt.refresh 

if i use the following, it works great:

 dt.recordsource="Select * from Table_Name WHERE Field1 like '" & combo1.text & "'"
dt.refresh 

so i guess i use wrong syntax after 'WHERE' parameter.

thanks in advance guyz

[andrewsw]

It might be because you are using LIKE but you haven't supplied any wildcards. They may be * and ?, or % and _, depending on your database system. Alternatively, use equals = if you are not using wildcards.

This post has been edited by andrewsw: 26 January 2013 - 04:12 PM

[valerov]

i replaced "like" with "=" but i keep getting the same error. I think its because i use the WHERE statement with wrong syntax. if i use "WHERE field like combobox1" and nothing else its running good. if i use "WHERE field like combobox1 AND field2 like combobox2 AND field3 like combobox 3 then i get the error

[maj3091]

Have you tried assigning your query to a variable and checking what it looks like in the immediate window once it's populated?

Are there any field type mismatches, looking at your query all fields appear to be strings, is that correct? Not sure whether this would cause that error or not.

An idea of the schema and data going in would be useful.

I'm no DB/SQL expert, so these are just observations.

[andrewsw]

Follow the advice given by maj3091. You could also try

dt.recordsource="Select * from Table_Name WHERE Field1 = '" & combo1.text & "'"
dt.refresh 

and repeat this for Field2 and Field3, separately. Then you might discover which of the three fields is the issue.

But store the SQL statement in a variable and post it here.

[guyfromri]

In my experience this error usually relates to a table name or a field name spelled wrong. If you look at it too long you'll never see it. Hand type each field name, combo name and table name slowly to see if it works.

[andrewsw]

I should whisper this but "Too few parameters" can also be an indicator of a corrupted database

[thava]

to my consideration the combo box text has some single quote character that's why this error will popup
seems the combo box text has
some thing like this
Shakespeare's Romeo and Juliet

so the solution is you need to use the parameter search this will solve your problem

[BobRodes]

andrewsw, on 26 January 2013 - 05:11 PM, said:

It might be because you are using LIKE but you haven't supplied any wildcards. They may be * and ?, or % and _, depending on your database system. Alternatively, use equals = if you are not using wildcards.

Like and = are equivalent if there are no wildcards. Like doesn't error out if there aren't any.

This post has been edited by BobRodes: 31 January 2013 - 11:06 PM

[BobRodes]

thava, on 28 January 2013 - 10:09 PM, said:

to my consideration the combo box text has some single quote character that's why this error will popup
seems the combo box text has
some thing like this
Shakespeare's Romeo and Juliet

so the solution is you need to use the parameter search this will solve your problem

I was thinking the same thing. If so, you can do this for each of your combo boxes:

Replace(comboX.Text, "'", "''")

If you want a literal ', then in SQL you double it, so: ''. For example: O''Malley.