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
stankstankAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tovvenkiCommented:
Hi,
see whether the following discussion helps you

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

regards
Venki

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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!
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
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?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.