SqlDataAdapter.Update doesn't work

Question

I'm using SqlDataAdapter.Update(DataTable) to throw a table at the database, but the SqlDataAdapter ignores my InsertCommand to write its own, which only sends the primary key and all the rows that can be null if they want. How do I get it to behave?

I step through the code before and after I call Update(). Before, it's my InsertCommand. After, it's the SqlDataAdapter's.

Edit: I don't especially want to post code samples because I can take the row I have and write my own SqlCommand object that works easily enough. I'm more interested in reasons why Update would decide that the InsertCommand I pass it isn't good enough so I can go digging through my own code -- this whole thing was supposed to be a timesaver.

Can you be more specific as to which bit of the code? I'm not doing anything other than calling SqlDataAdapter.Update(DataTable) once I'm done. — Merus
– Merus, Commented May 7, 2009 at 4:38

Merus · Accepted Answer · 2009-05-07 05:36:48Z

2

Right, after lots of digging I found out that I needed to call EndEdit on my rows when I was done with them so the changes I made weren't being discarded by the DataTable. As I said, I wasn't doing anything other than calling SqlDataAdapter.Update(DataTable).

edited May 7, 2009 at 5:36

answered May 7, 2009 at 5:24

Merus

8,9945 gold badges31 silver badges41 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Avindra Goolcharan Over a year ago

Thank you, good sir! This is exactly what I needed! BindingSource.EndEdit() before DataAdapter.Update() does the trick.

Collectives™ on Stack Overflow

SqlDataAdapter.Update doesn't work

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related