George,

Please share a sample containing your attempt a creating the editor provider that reproduces the error 'Unable to create editorprovider' so that we can review what is happening.

Pete,

I recommend starting a new thread and including more details and including an example if possible.  At least include the relevant code that you are using.

Activation and Selection are different concepts.  There can only be one active node/cell at a time while there can be many selected nodes.  I believe you will want to use the SelectMultiple method.  You should be able to see an example of this if you record selecting multiple items.

Wei,

The UltraWebGrid was retired in 2011 and hasn't been supported since the spring of 2014.

I see that you are still using the release of 2011 Volume 1 and you may want to test your application with the latest service release as there may be bug fixes that are relevant.

If the latest service release doesn't address the issue, if you are able to provide a sample that reproduces the issue, I will be able to take a look and give you a suggestion on a work around or solution.

If you aren't able to reproduce it in a sample, you may want to download our source code and see if you can debug it on your own to see what specifically is causing the exception.  This might give you an idea on a solution or the additional information may help me give you a suggestion.

Note that it is also recommended that you consider replacing the grid with our Ignite UI for JavaScript igGrid or igHierarchicalGrid as they have better support for modern web browsers.

Selvi,

Paging is something that would need to be manually implemented outside the grid by binding the grid to a subset of your data. 

One of the challenges that you will have is that the built in summaries that you are already using require access to all of the data to work so you would need to use external summary calculations that are just displaying data that was retrieved from the back end as Mike suggests.

Note that it is likely that you can reduce the amount of memory needed by the grid by using a load on demand approach with the UltraDataSource and the external summary calculations.

You may also want to review the Memory Usage section of the UltraGrid performance guide to see if there are any other optimizations that you can make in your application.

Let us know if you have any questions.

Thank you for sharing Ron,

It is possible that others in the community will benefit from this information.

The red X happens for any unhandled exception during paint in windows forms.  The threading issue is the one that we see the most often.  Other less common scenarios that I have seen include errors in a CreationFilter, DrawFilter, or DataFilter.

The Initialize client event fires after the JavaScript object is created.  You can see all client event of the grid in the API documentation by looking at the GridClientEvents members.

An approach more like what the UltraWebGrid allowed in your example would be to set the value in the DataSource that you are binding the WebDataGrid to before binding.  If the column/property doesn't exist in your DataSource currently, you should consider adding it as it is a better approach than initializing the value on the client side.