Error 3061. Too few parameters. Expected 1.

[Glenn_Suggs]

This error keeps popping up from time to time and for the life of me I can't see where it's coming from. I have parameters passed to the SQL in the form of string variables so I don't see the problem. Any help with this would be greatly appreciated. It seems a simple enough SQL statement. Just returning a record from which I want to use the fields' values. Thanks in advance.

strWorkOrderKey = "123456V"
strNetwork = "BUT50"
strLocNum = "84-26"
strLocationID = "1234567890123456"

strSQL = "select * from wo1 w, wov001 wv " & _
                         "where w.wo1_key = wv.wo1_ptr " & _
                        "and w.wo1_key = '" & strWorkOrderKey & "' " & _
                        "and w.code = '" & strNetwork & "' " & _
                        "and w.location = '" & strLocNum & "' " & _
                        "and w.locationid = '" & strLocationID & "'"
set rsWO = CurrentDB.OopenRecordset(strSQL, dbOpenSnapshot)

[orange]

Need to see your table layouts/fields.
But , there is an error here
CurrentDB.OopenRecordset(strSQL, dbOpenSnapshot)

3061 can often be from a spelling mistakes.

[John_G]

It is more likely that the spelling mistake is in a reference to one of the fields in Wol or wov001; that is the first place I look when I get that error.

e.g. should locationid be location_ID?

[pbaldy]

On top of those thoughts, is it really is intermittent (as implied by "from time to time")? If so, I'd suspect a data issue rather than a spelling mistake. Could any of the variable values have an apostrophe or quotes in them? They appear hard-coded here, but I assume in real life they aren't.

[June7]

Maybe:

strSQL = "select * from wo1 AS w, wov001 AS wv " & _

But since you say the statement usually works, this is probably not relevant.

If values have ' or " in the string, such as O'Hare or 18", going to be an issue in the compiled statement as noted by Paul. Need to double the character. The apostrophe is easy to handle with Replace() function but this is why I try to prevent data with quote marks.

However, judging by the fieldnames and example values, this does not appear to be type of data to contain ' or " punctuation but not impossible.

[pbaldy]

In my experience the "AS" is optional. Works without for me in Access and SQL Server.