Sorry for this delayed reply Frans. I took some time to gather info from the radgrid manual.
Have you tried by following their way of tracking TEMP changes ? I mean: does the grid then send all changes to the datasourcecontrol in one go when you click save?
No. It is not happening. With LivePersistance = False, and no code in the PerformWork (am I right?), when I edit something and hit Update, the grid rebinds automatically (even in Ajax Mode) and bring the data from the Server, which is old values ofcourse.
I found this info in the grid manual
Why does it require re-binding?
Getting the latest data from the grid source ensures the consistency of the displayed information. That is the reason why r.a.d.grid performs automatic rebind when the user switches the grid item in edit mode.
Creating edit form and populating its fields with data on the client is not secure as at the same time other users may change the database content. This will result in data inconsistency.
Moreover, the entire process of client edit form generation and its subsequent submit on the server (to reflect the changes) will tremendously slow down the control's performance. That is why our developers have not included this feature in the current grid implementation.
It means, it cannot postpone the rebind of the grid until I hit "Save" button outside grid. Am I right?
If it is not going to work, I need to find the workaround.
The Grid has UpdateCommand, InsertCommand and DeleteCommand events. But If I bind with LLBL's Datasource control, I do not need to use them. Also it has ItemUpdated, ItemDeleted and ItemInserted events which fires "After" the Update, Delete and Insert operations.
Can you see what I can do with these events to make use of UOW and save it in one go?
Thank you for your patience.