>Thank you for your recommendation. What I found, so far, working consistently is following (in pseudo code):
>1. Call .HasVersion() on the row that user may or may not have changed (I only allow user to work on one row at a time)
>2. If the 1. (above) is True, call .EndEdit() on the row that user made changes
>3. At this point I thought I would get the DataSet of changes and send it to the BIZ/DAL for validation. But I changed my mind since the dataset of changes has all columns. So I might as well send to the BIZ/DAL the row on which user made changes.
>4. Perform validation on the changed row and other nonsense before sending it to DAL/Stored procedure for update.I think for 1) you mean .HasVersion(DataRowVersion.Proposed).
For any lurkers out there who aren't sending only one row to the back-end at a time, and want to know about GetChanges and Proposed row state, I recommend reading a short post on my blog:
http://geek-goddess-bonnie.blogspot.com/2009/09/fun-with-datasets.html~~Bonnie