In case the user hits Escape key (27) we will just get out of the edit mode by calling Cancel Edit method.
Once Update Edit is called a callback will be generated and the Row Updating server side method will be executed, in which we will need to handle the persistence of the data.
We need to attach the following method to the Row Updating event: What happens in this event is that a request for updating rows is sent.
We will receive the old values that (of interested updating columns) and the new one that were chosen by the user, in a form of Ordered Dictionaries, exposed by two properties in our event argument.
No more code is necessary for managing data and we can now comfortably start with the interface. There are several methods for achieving the same result.
If you are interested in more you can check this Grid Editing – Edit Modes A rich set of editors for different column types allows column values to be modified with ease.
I will not go in the detail about the environment and developing requirements, if interested jump op to my other posts.
The attached project is written in Visual Studio 2012. Also you will need a Microsoft SQL Server 2012, Express or and more advanced version will be just fine.
Check this post about how to get the Dev Express controls and on how to eventually upgrade the project The only exception is the Remove Credit Card method, which actually doesn’t delete the item and in cascade the related items in the tbl_Import, but only flags the credit card as inactive.In order to make this thing actually work, we need to modify the stored procedure that we defined in previous post sp_Get Credit Card Imports.If you run the example right now and double click on a row, you should see something similar to this: Even if this looks nice and simple, you maybe noticed that the fields are not editable.This is because we didn’t binded our grid to a valid and well defined Data Source.Because of this, we have our edit controls in read only state.