• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 249
  • Last Modified:

FormView error: too many arguments specified

I put a formview on my webpage so I can insert and edit records.  It does not work properly... I get an error stating that it has too many arguments, but I can't figure out what is wrong.  There is no clear message, it's just vague - the stored procedure takes exactly as many parameters as I am passing in.  I must be missing something, but I can't figure it out.  I have worked with the formview and changed the parameters.  I have exactly aligned the parameters of the SP with the parameters passed from the formview. It just doesn't work.

Here is the exact error that I receive:
---------------------------------------------------------
"Procedure or function INS_SERVICECALLS_InsertNewServiceCall has too many arguments specified."

I have tried to put the Stank on this error, but in the end I had no luck.  Any help you can give is greatly appreciated.

- Stank Stank
0
stankstank
Asked:
stankstank
  • 3
1 Solution
 
tovvenkiCommented:
Hi,
see whether the following discussion helps you

http://geekswithblogs.net/chrishan/archive/2005/07/02/45278.aspx

regards
Venki
0
 
stankstankAuthor Commented:
I would really like to know how to fix this - the biggest problem is that I don't exactly understand what is going on.  Please help!
0
 
stankstankAuthor Commented:
Unfortunately that wasn't the fix - here is my insert block (html):

                                    <InsertParameters>
                                        <asp:Parameter Name="Office_ID" Type="Int32" />
                                        <asp:Parameter Name="FK_Technician_ID" Type="Int32" />
                                        <asp:Parameter Name="FK_Priority_ID" Type="Int32" />
                                        <asp:Parameter Name="FK_Category_ID" Type="Int32" />
                                        <asp:Parameter Name="FK_Status_ID" Type="Int32" />
                                        <asp:Parameter Name="FK_Contact_ID" Type="Int32" />
                                    </InsertParameters>

// Please note - they are all prefixed with 'FK_' because I was trying to standardize the names because of this error.  It did not fix the problem.

-Stank
0
 
stankstankAuthor Commented:
Ok, I have eliminated the problem.  My stored procedure sends back a column called 'Contact'.  it is not needed for updating, because the contactID is for this (which is also returned).  

I don't understand why select/update are so closely tied together.  Is it is the same with insert?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now