OleDbException: Too many arguments.

[jn]

Hi,

I'm passing around 30 arguments to a stored procedure, and
I got the following error (see below).
It works fine if I narrow down to around 25 args. Is there
any workaround to bypass this exception, I need to pass 30
of them to my stored procedure. Thanks.
I'm using Framework 1.0.

-----------------------
Too many arguments.
Description: An unhandled exception occurred during the
execution of the current web request. Please review the
stack trace for more information about the error and where
it originated in the code.

Exception Details: System.Data.OleDb.OleDbException: Too
many arguments.

Source Error:
Line 663:
Line 664: 'execute SQL
Line 665: oCmd.ExecuteNonQuery()
Line 666:
Line 667: 'Catch exc As OleDbException
--------------------------

[Bill Priess]

If you have any return parameters, they must be specified first. You should
declare any return parameters before you start adding input parameters. That
is commonly the reason for this error. Also, make sure that the order in
which you are adding your parameters match the order in the stored
procedure.

HTH,
Bill P.
"jn" <an*******@discussions.microsoft.com> wrote in message
news:00****************************@phx.gbl...

Hi,

I'm passing around 30 arguments to a stored procedure, and
I got the following error (see below).
It works fine if I narrow down to around 25 args. Is there
any workaround to bypass this exception, I need to pass 30
of them to my stored procedure. Thanks.
I'm using Framework 1.0.

-----------------------
Too many arguments.
Description: An unhandled exception occurred during the
execution of the current web request. Please review the
stack trace for more information about the error and where
it originated in the code.

Exception Details: System.Data.OleDb.OleDbException: Too
many arguments.

Source Error:
Line 663:
Line 664: 'execute SQL
Line 665: oCmd.ExecuteNonQuery()
Line 666:
Line 667: 'Catch exc As OleDbException
--------------------------

[JN]

arg, I found out it's Visual FoxPro problem (I'm using VFP
as the backend database), it just won't take more than 28
parameters. Thanks, Bill, for looking into my problem
though.

-----Original Message-----
If you have any return parameters, they must be specified first. You shoulddeclare any return parameters before you start adding input parameters. Thatis commonly the reason for this error. Also, make sure that the order inwhich you are adding your parameters match the order in the storedprocedure.

HTH,
Bill P.
"jn" <an*******@discussions.microsoft.com> wrote in messagenews:00****************************@phx.gbl...

Hi,

I'm passing around 30 arguments to a stored procedure, and I got the following error (see below).
It works fine if I narrow down to around 25 args. Is there any workaround to bypass this exception, I need to pass 30 of them to my stored procedure. Thanks.
I'm using Framework 1.0.

-----------------------
Too many arguments.
Description: An unhandled exception occurred during the
execution of the current web request. Please review the
stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.OleDb.OleDbException: Too
many arguments.

Source Error:
Line 663:
Line 664: 'execute SQL
Line 665: oCmd.ExecuteNonQuery()
Line 666:
Line 667: 'Catch exc As OleDbException
--------------------------

.