Comments by Joe Fager

Joe Fager 22-Sep-12 1:27am View

That is probably what I will do. That makes it real easy because all I have to do is check the dataset for changes. dataset.haschanges and handle it from there. I made it a lot harder than it needed to be. I will be wanting to validate the controls individually anyway. As soon as the first validation event fires and passes I can enable the save button, and if they leave the form or the record, I can ask them to save changes.

Joe Fager 22-Sep-12 1:26am View

Deleted

That is probably what I will do. That makes it real easy because all I have to do is check the dataset for changes. dataset.haschanges and handle it from there. I made it a lot harder than it needed to be. I will be wanting to validate the controls individually anyway. As soon as the first validation event fires and passes I can enable the save button, and if they leave the form or the record, I can ask them to save changes.

Joe Fager 21-Sep-12 17:32pm View

Thank you very much... I do think that this will work. I can't test it right now, but will not let your work go to waste. I will test it later. Thank you kindly. It makes sense to me and I can already see how it would work in VB.

Joe Fager 21-Sep-12 14:07pm View

Yes, I understand this solution. However, I don't know when to check the RowState Property.

I want to check this before the user leaves the form or moves to another record. That way I can ask if they would like to save changes on that record before proceeding. So it would need to be an event such as BindingSource.CurrentChanged the problem with that is it happens after the user navigates to another row.

Comments by Joe Fager (Top 4 by date)