Hello Frank,

This is a very good question, and I am sure other folks might be interested to know it as well. To answer your question, can one simply replace a WebGrid out of their forms and place the WebDataGrid and it will work and behave just like the WebGrid? The answer is No. It all depends on how much work is being done within the WebGrid a part from displaying data. Just so that you know, when we were working on the WebDataGrid, we did want to have an easier transition path, if possible for users, but it turned out to maintain the ease of use and light architecture, we had to implement it differently.  

So, I'd recommend you start off by checking the WebDataGrid features and see if they fulfill the grid requirements that you have on your pages. Once you know they do, you should then use the WebDataGrid for any future pages that you build, or any new applications you write. If there is a feature like Outlook GroupBy that the WebDataGrid doesn't support at the moment, and you need to have it on your page, then you can still use the WebGrid.

Finally, for the pages that has the WebGrid already and now you want to convert them to use WebDataGrid, then it can be done on a grid by grid basis, taking one at a time, hooking it up to your datasource, enabling the behaviors you want, and implement client and server activities.  

I hope this explains what you were looking for.

Regards,

Taz.  

For new screens when should one use the WebGrid vs WebDataGrid? 

I've got screens built on the WebGrid now, should I invest the time to change them?  Is there any way it's as simple as replacing the control on the page?  Does all the AJAX behind the scenes including client side javascript and servers side events, methods and properties?

 Thanks,

Frank