the SQL side and not in the grid or dataset.
use sql profiler to capture the sql statement.
paste it into query analyzer and debug the sql.
once you know what the problem is, finding where it's being
caused may be easier.
-----Original Message-----
I am having almost constant problems with these bound Datagrids in my VB.NETWeb Forms app.
I got one working just fine but this last one is just a killer. Right when Ipass back my dataset and call the update method (from doing an update on thegrid), it bombs with that rediculously generic SQL error (BIG HELP MS!!).
How do I debug this thing? I took all of the contraints off the table. Imade sure that I am sending back the exact same parameters (in the sameordinal position) as to update as are in my select (same datatypes). I checkeach item in the immediate window no nulls or odd data. I am putting thename of the Dataset table in the update method: Dataset.Update(MyDataSet,"MyTableName"), What gives???
You know if MS wants us to use these bound controls they are going to haveto make things a little more straight forward.
.