Occassionaly (and its rare, but i think there are repo steps to this, i just
cant completely determin them, but here is what I figured out so far)
I have a data set (say its called DS)
I have three tables... call them people, peoplejunitem and item...
peoplejunitem is a many to many junction table between people and items...
well say I load one set of information about a person into the data set's
tables... ok this person has items in the junction... say I alter the
information in the junction but dont commit it to the database... now I go
and load another person... but while loading the next person it clears the
information in the junction table and the person table and replaces it with
the 2nd person... ok I make changes and push the data back to the
database... and boom error... zero rows updated when 1 was expected to be...
well that one row updates was from the FIRST! person... even though I did a
ds.table("PersonJunItems").rows.clear somehow it still thinks it has rows to
push! why?! this happens randomly to me! I tested out the T-SQL statements
like crazy and they are not at fault, they are return the correct response,
but while watching the SQL Server profiler I saw the commands to update the
pervious person going through on person 2 to the database... any ideas how
to stop this or fix the problem? or anyone ever see anything similar to
this? thanks!