Like Cor mentioned, EndCurrentEdit will give you what you are after if I
understand the question correctly. But note that you are editing the data
directly - it's just that it's in Edit mode and moving the 'cursor' merely
ends the edit. I only mention this b/c the verbiage you use w/ cursors and
all may be causing some confusion. When you navigate through your
datatable, this is all happening locally - nothign happens on the db side
until you call .Update or you manually fire a query to send that data back.
To that end there's not really a cursor at all, at least in the ADO 2xxxx
sense. Anyway, there's a pretty good reason for this all. Let's say that
you have a column (int) that's bound to a dataview (or a datatable's
defaultview) and it's sorted on a given column. let's say that you want to
change the value 2 to 12. You wouldn't want to position of your row moving
as soon as you hit 1 b/c after all, you're going to hit 2 next and make it a
12. So EndCurrentEdit ends the EditMode - and the editmode basically tells
the bindings to hold on while the editing is being done. Nothign will
happen at that point until you indicated that you are finished. So if you
edit one of your textboxes for instance, and check the rowstate of that row,
it will say unchanged even though you've 'changed' the data. However as
soon as you move out of there or call EndCurrentEdit, if you check the
rowstate again it will indicate a modification. Probably sounds like
parsing words but the distinction is somethign that can defintiely give you
some grief if you aren't aware of it - at least it sure did for me once upon
a time ;-)
--
W.G. Ryan MVP Windows - Embedded
Have an opinion on the effectiveness of Microsoft Embedded newsgroups?
Let Microsoft know!
https://www.windowsembeddedeval.com/community/newsgroups