G
Guest
Using SqlDataSource controller with sprocs and its been working fairly well.
I changed a table by removing a foreign key, removing 2 columns and adding 3.
I rewrote the update sproc and works fine as long as I don’t use it on the
sqlDataSource control.
Using it on the SqlDataSource control I get the error that to many
parameters are being specified which makes sense because the old sproc had 1
less parameter.
Now things get strange!
I re-created the sproc with a new name, created a different sproc with only
a few parameters AND ran the whole thing on a different machine using a
virgin project. I got the exact same error is all cases. I have another table
that works nearly exactly the same and I ran it in the new application and it
works perfectly.
Now it’s a very simple setup I have in my isolated application. A simple
grid with simple CRUD sprocs and the select is fine. Its update that is an
issue.
I personally think it’s a reference to the old sproc signature somehow
hiding within SQL 2005 itself. I am not familiar with out SQL creates its own
schema but that is where I think the issue is.
I changed a table by removing a foreign key, removing 2 columns and adding 3.
I rewrote the update sproc and works fine as long as I don’t use it on the
sqlDataSource control.
Using it on the SqlDataSource control I get the error that to many
parameters are being specified which makes sense because the old sproc had 1
less parameter.
Now things get strange!
I re-created the sproc with a new name, created a different sproc with only
a few parameters AND ran the whole thing on a different machine using a
virgin project. I got the exact same error is all cases. I have another table
that works nearly exactly the same and I ran it in the new application and it
works perfectly.
Now it’s a very simple setup I have in my isolated application. A simple
grid with simple CRUD sprocs and the select is fine. Its update that is an
issue.
I personally think it’s a reference to the old sproc signature somehow
hiding within SQL 2005 itself. I am not familiar with out SQL creates its own
schema but that is where I think the issue is.