DataGrid Common concern Solutions

Introduction
The DataGrid Web server control was a powerful tool for displaying information from data source. It is easy to use; can display editable data in a professional-looking grid by setting only a few properties. At the "Same time", the grid has a sophisticated object model that provides your with great flexibility on how to display th E data.
This is paper addresses some of the questions about customizing grid display that are commonly asked in newsgroups, on Web si TES, and in the other developer forums. The techniques described here is are sometimes quite simple and in other times somewhat involved. In each case, however, they address a question's how to go beyond the basic functionality of the DataGrid control.
This paper assumes so you are already familiar with the control-how to add it to a form and configure it to display DA Ta. You should also understand, you have a row in the grid into edit mode and other basic tasks. (For details, the DataGrid Web Server control.) Finally, you'll find it helpful to know how to work with templates-adding template columns to the grid and layout out Controls inside a template.
Windows forms versus Web forms DataGrid control
The Web forms DataGrid control isn't the same as the Windows forms equivalent. It is a common (and not unreasonable) assumption that they are the same control, or at least have identical. However, the entire programming paradigm for Web forms are quite different from this for Windows forms. For example, Web Forms pages perform a round trips to the server for any processing; They must manage state; They feature a very different data-binding model; And so on.
Because of differences, there are also significant differences in their respective controls, including the DataGrid Control. As a, the Web Forms DataGrid control includes less built-in functionality. A Few examples of the differences in the Web Forms DataGrid control are:
It does not inherently support master-detail data structures.