Access 2000 Too Few Parameters: Expected 1

  • Thread starter Thread starter SPS
  • Start date Start date
S

SPS

I am responsible for a small academic web that makes an online directory
available by using an Access 2000 database with asp code in a FP (2003) web
on an NT server.

This society has a new secretary and they sent an updated Access file to me
that generates this error:

Microsoft OLE DB Provider for ODBC Drivers error '80040e10'
[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 1.

/membersonly/directory/listing.asp, line 150

I don't know what to do and would appreciate some help. I have searched NGs
and Microsoft support.
 
The new secretary probably deleted or renamed one or more
columns in the database table. Your options are:

o Restore the missing columns or column names so they
match what the Web page is looking for.

o Updat teh Web page so it uses the new column names.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
|| Microsoft FrontPage Version 2002 Inside Out
|| Web Database Development Step by Step .NET Edition
|| Troubleshooting Microsoft FrontPage 2002
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------
 
Just an FYI - The Access "Too Few Parameters" error, in the context of an
ASP web interface, almost always indicates that some object referenced in
the SQL query is either spelled wrong or the wrong name. Access handles
parameterized queries in such a way that when it parses the SQL query, any
words it doesn't recognize, and can't map to a database object, are treated
as input parameters. Since the query you pass into SQL Server is not
supposed to be a parameterized query, Access has no value to give for the
"parameter" and issues this error.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Jim Buyens said:
The new secretary probably deleted or renamed one or more
columns in the database table. Your options are:

o Restore the missing columns or column names so they
match what the Web page is looking for.

o Updat teh Web page so it uses the new column names.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
|| Microsoft FrontPage Version 2002 Inside Out
|| Web Database Development Step by Step .NET Edition
|| Troubleshooting Microsoft FrontPage 2002
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------


-----Original Message-----
I am responsible for a small academic web that makes an online directory
available by using an Access 2000 database with asp code in a FP (2003) web
on an NT server.

This society has a new secretary and they sent an updated Access file to me
that generates this error:

Microsoft OLE DB Provider for ODBC Drivers error '80040e10'
[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 1.

/membersonly/directory/listing.asp, line 150

I don't know what to do and would appreciate some help. I have searched NGs
and Microsoft support.


.
Click to expand...
Click to expand...
 
Thanks for these explanations. However since I know nothing about Access and
did not write the asp code (and don't know how to fix it), I will need to
seek professional help.

Harold
Kevin Spencer said:
Just an FYI - The Access "Too Few Parameters" error, in the context of an
ASP web interface, almost always indicates that some object referenced in
the SQL query is either spelled wrong or the wrong name. Access handles
parameterized queries in such a way that when it parses the SQL query, any
words it doesn't recognize, and can't map to a database object, are treated
as input parameters. Since the query you pass into SQL Server is not
supposed to be a parameterized query, Access has no value to give for the
"parameter" and issues this error.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Jim Buyens said:
The new secretary probably deleted or renamed one or more
columns in the database table. Your options are:

o Restore the missing columns or column names so they
match what the Web page is looking for.

o Updat teh Web page so it uses the new column names.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
|| Microsoft FrontPage Version 2002 Inside Out
|| Web Database Development Step by Step .NET Edition
|| Troubleshooting Microsoft FrontPage 2002
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------


-----Original Message-----
I am responsible for a small academic web that makes an online directory
available by using an Access 2000 database with asp code in a FP (2003) web
on an NT server.

This society has a new secretary and they sent an updated Access file to me
that generates this error:

Microsoft OLE DB Provider for ODBC Drivers error '80040e10'
[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 1.

/membersonly/directory/listing.asp, line 150

I don't know what to do and would appreciate some help. I have searched NGs
and Microsoft support.


.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top