My application contains hundreds of UltraWebGrids that need to be converted in order to stay current. I am converting the first grids in order to set an example for others to follow. I am finding it difficult to know how to use the properties of EnableAjax, EnableAjaxViewState, EnableDataViewState and EnableViewState. As part of this convertion we would like to speed up our application. I know carrying around ViewState slows things down but I do not see a way around this for an editable grid where we get our data from a SQL datasource. If I turn off EnableDataViewState, I have to bind my data on every post-back and lose the changes the use entered.
Is there suggestions on when to set these values to true or false?
We ended up with #2. This has worked the best for us for most grids.
#2. Set EnableDataViewState="false" and save the grid's data in session and rebind (grid.DataSource=Session DataTable) on every post-back.
Hi Autumn, I know it has been a long time, but did you ever figure this out? I'm struggling with the same issue now.
What are the best combinations to use when Batch Update is set to true for the grid?
I am still questioning if it is better to:
#1. Set EnableDataViewState="true" and carrying the grid's data around, only binding the data once.
When I originally tried #2, I thought the user's changes in the grid would be lost but I see the grid somehow manages this.
Hello IntegraSys76,
Let me know if you need further information regarding this question.