[RESOLVED] too few parameters, expected 1

I have a VB6 app running against an Access2000 database. I have the following bit of code to generate a SQL statement:

Code:

---

strSQL = "select distinct QCType, LowValue, HighValue from " & strSpecsTable
    strSQL = strSQL + " where ShortName = """ & FieldName & """"

---

When this is run it produces a perfect SQL statement. It looks exactly like what I am looking for. The value coming up in the Immediate window is:

Code:

---

select distinct QCType, LowValue, HighValue from tblDataSpecs_v1_0 where ShortName = "CRITERIA"

---

I copy and paste this directly into the Access DB and it runs beautifully. I have checked my connection string, that is all perfect and running against the correct database. Still, I am getting "Too few parameters. Expected 1" each and every time I allow the program to execute this statement. What am I missing?

HELP!!!! Thanks!

Thread moved to 'Database Development' forum (the 'VB6' forum is only meant for questions which don't fit in more specific forums)

The most likely cause is your use of " around the text value, whereas you should be using ' instead.

This is Access. The ' character would be for SQL or Oracle. Access encloses text values with " marks.

Any other ideas?

Quote:

---

Originally Posted by evaleah

This is Access. The ' character would be for SQL or Oracle. Access encloses text values with " marks.

Any other ideas?

---

Access can also use ' Single Quotes.

Have you at least given it a shot?

Honestly, I had not and it worked. Weird. I still wonder why all my other SQL statements with " marks work and this one didn't but I guess I will never know.....

An important point is that you are not actually using Access, you are just using an .mdb file (which for obvious reasons is known as an Access database) via Jet or ACE.

There are some differences between the SQL interpreter used in Access itself and the ones used in Jet/ACE.


I'm not entirely sure how Jet/ACE treat values inside " marks, but I recommend changing them all to ' if you can - because it might be treating those items as field names rather than values, and thus doing the wrong thing.

It occurred to me later that everything I had done recently was in DAO which didn't work with ' marks. Since I am more of a SQL Server programmer than an Access one I had had all kinds of issues with those marks about a week ago. Oh well... Thanks again for the tip and your patience.

Please mark this thread as "RESOLVED", if you don't have any more issues.