Too Few Parameters? I don't get it ... looks ok to me.

[Sue Bricker]

Hi, again.

I have a piece of code behind a form that is producing the following
error:

"Too few parameters. Expected 1."

However, it certainly looks like I have the parameters there. Here's
the code:

Set db = CurrentDb
strSQL = "SELECT tblDogs.ID as dogID FROM tblDogs " & _
"WHERE tblDogs.exhibitorID = " & Me!ID
Set rsd = db.OpenRecordset(strSQL)

The error occurs on the "Set rsd ..." statement. The db is defined as a
DAO.database and rsd is defined as a DAO.recordset.

Any ideas?

Thanks.
SueB

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Allen Browne]

The request for a parameter indicates that there is something Access does
not understand.

Is there a field named ID in tblDogs?
Is there a field named ExhibitorID (with no space)?

What type of field is ExhibitorID? If it is a Text type (not a Number type),
you need extra quotes:
"WHERE tblDogs.exhibitorID = """ & Me!ID & """;"

Is there a value in the text box ID at the time you receive the error?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Sue Bricker" <sb****@att.net> wrote in message
news:42**********@127.0.0.1...

Hi, again.

I have a piece of code behind a form that is producing the following
error:

"Too few parameters. Expected 1."

However, it certainly looks like I have the parameters there. Here's
the code:

Set db = CurrentDb
strSQL = "SELECT tblDogs.ID as dogID FROM tblDogs " & _
"WHERE tblDogs.exhibitorID = " & Me!ID
Set rsd = db.OpenRecordset(strSQL)

The error occurs on the "Set rsd ..." statement. The db is defined as a
DAO.database and rsd is defined as a DAO.recordset.

Any ideas?

Thanks.
SueB

[Grumpy Old Man]

Sue Bricker <sb****@att.net> wrote:

I have a piece of code behind a form that is producing the following
error:

"Too few parameters. Expected 1."

However, it certainly looks like I have the parameters there. Here's
the code:

Set db = CurrentDb
strSQL = "SELECT tblDogs.ID as dogID FROM tblDogs " & _
"WHERE tblDogs.exhibitorID = " & Me!ID
Set rsd = db.OpenRecordset(strSQL)

The error occurs on the "Set rsd ..." statement. The db is defined as a
DAO.database and rsd is defined as a DAO.recordset.

Hi Sue, a couple of things to check.

Is "ID" a text box? It's generally good practice to name controls with a
prefix, ie your text box would be named txtID so there would be no
ambiguous references.

Also, if txtID's data source type is "text" then you would need to use
quotation marks:

strSQL = "SELECT tblDogs.ID as dogID FROM tblDogs " & _
"WHERE tblDogs.exhibitorID = '" & Me!txtID & "';"

Regards,
Keith.
www.keithwilby.com

[Sue Bricker]

Allen,

Is there a field named ID in tblDogs?
YES. This is an autonumber (long int).

Is there a field named ExhibitorID (with no space)? YES
This is a long int in the tblDogs record. (connecting Dog record to
Exhibitor record)

What type of field is ExhibitorID? Long int

If it is a Text type (not a Number type),
you need extra quotes:
"WHERE tblDogs.exhibitorID = """ & Me!ID & """;"
Not a text field.

Is there a value in the text box ID at the time you receive the error?
Actually, I don't have an ID text box in the Exhibitor form. The form
is based on a query against the frmExhibitors. ID is the key of the
Exhibitor Record. I know that there is a valid value in me!ID because I
displayed it in debug mode in the 'Immediate window'. It's a valid
integer.

Now ... any ideas : )

Thanks.
Sue

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Allen Browne]

No, that all looks right.

To debug it, add:
Debug.Print strSQL
just before the OpenRecordset line.
Run the code.
When it fails, look at what printed in the Immediate Window (Ctrl+G).

If that still looks right, try copying that, and pasting into SQL View of a
query. Does it work? Can you see what's wrong? Does the name of the
requested parameter now help you identify what name it does not recognise?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Sue Bricker" <sb****@att.net> wrote in message
news:42**********@127.0.0.1...

Allen,

Is there a field named ID in tblDogs?
YES. This is an autonumber (long int).

Is there a field named ExhibitorID (with no space)? YES
This is a long int in the tblDogs record. (connecting Dog record to
Exhibitor record)

What type of field is ExhibitorID? Long int

If it is a Text type (not a Number type),
you need extra quotes:
"WHERE tblDogs.exhibitorID = """ & Me!ID & """;"
Not a text field.

Is there a value in the text box ID at the time you receive the error?
Actually, I don't have an ID text box in the Exhibitor form. The form
is based on a query against the frmExhibitors. ID is the key of the
Exhibitor Record. I know that there is a valid value in me!ID because I
displayed it in debug mode in the 'Immediate window'. It's a valid
integer.

Now ... any ideas : )

Thanks.
Sue

[Sue Bricker]

Allen,

One more piece of information ...

The variable strSQL is defined as:

"SELECT tblDogs.ID as dogID FROM tblDogs WHERE tblDogs.exhibitorID =
329"

after the assignment statement (from debugging).

Thanks.
SueB
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Sue Bricker]

Keith,

"Is "ID" a text box? " No. ID is the autonumber key of the
tblExhibitor record. And YES you are right about naming conventions. I
try to name my variables inside procedures and modules using a
convention. However, I HAVE been laxed in my naming conventions (or
lack thereof) in record field names. So ... I agree with you.

Thanks for you input.

SueB

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Sue Bricker]

Allen,

ThankyouThankyouThankyou! Using the SQL view of Query was the thing I
needed. So, now my face is really RED. There is no field "exhibitorID"
in tblDogs. It is "exhibitor_ID". And I wrote this stuff!!!

Thanks very much.

SueB

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Allen Browne]

Yep: we've all done that kind of thing, Sue.

And now you have learned another way to get Access to help you track down
what the problem is. It's a pretty powerful development environment.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Sue Bricker" <sb****@att.net> wrote in message
news:42**********@127.0.0.1...

Allen,

ThankyouThankyouThankyou! Using the SQL view of Query was the thing I
needed. So, now my face is really RED. There is no field "exhibitorID"
in tblDogs. It is "exhibitor_ID". And I wrote this stuff!!!

Thanks very much.

SueB