Sam,

I confirmed the situation you mentioned. However, I went a little further with it. It seems that the changes being made after clicking on a different row in the grid are still in memory and if you make other row changes and then save, all of those rows are saved.

This sounds like the transaction scenario you would like to have that started this thread. Now the challenge is to figure out why it happens and then harness it.

To try this yourself, go to one of your maintenance forms and make a change to the first record in the grid. Then navigate to the second record by clicking on the record in the grid so that the 'ask to save' does not get prompted. Make a change to the second record and do this one more time on the third record, change it and then click the 'Save' button. You will notice that all three saves took place.


>Since nobody responded with verification of the problem I was seeing when navigating away from a changed record by clicking on a different row in the mmDataGridView, I investigated it further until I am convinced it is a bug in MM .NET. I have reported it to Kevin and I await his solution.
>
>Sam
>