What is Error Number 3061?

[Lou_Reed]

In the db that I have attached the files runs with the error when it executes strSQL. It seems to have a problem with the statement.


CurrentDb.Execute strSQL, dbFailOnError





It generates an error :

Error number 3061
Too few parameters.Expected 1

I have checked the syntax and I have found nothing. Of course, that does not mean it is correct.

I am just unsure as to what is causing the error. Is there a way to make the error checking more explicit?

Anyway, how do I fix this error?

Respectfully,

Lou Reed

[pbaldy]

Something is wrong with the SQL, perhaps a misspelled object. You didn't say where in the db, but this is the standard debugging method:

BaldyWeb-Immediate window

If you don't see the problem, post the SQL here.

[Lou_Reed]

I tried what you said. I tried on the program that does not work and on the program that does work. The output was in the locals not the immediate window. I have attached both db programs and
screen shots of each. I am very confused why I am getting the Error 3061 on my db. Any other suggestions welcome.

Why is it in the locals not the immediate window? There seems to nothing shown here as to what is wrong.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[pbaldy]

Like I said, something misspelled. The field name is "ysnMeeting_Invite_Sent", not "ysnMeeting_Invite_SentID".

As to the window, I'm not sure. Your pictures don't show the Immediate window, which is where the SQL will be.

[Lou_Reed]

That worked. I am just wondering how it would be seen when I put the expanded version of it in the immediate window of the MS Access debugger.

I mean would this have become obvious?

Any help appreciated. Thanks in advance.

Respectfully,


Lou Reed

[pbaldy]

I wouldn't say obvious necessarily, but it's generally always helpful to see the finished SQL. It isn't always turning out like you expect. In this case, I didn't even run it. I just checked the names in the code against the names in the table.

[orange]

Lou,

See the debugging tips at Chip Pearson's site.
t says Excel, but its for vba generally.