Hi Gary,
Thank you for your post.
To understand why we introduce the new GridView control while DataGrid is
doing pretty good, we need to address two points:
1) While DataGrid is one of the most powerful controls in ASP.NET 1.x, it
requires too much work for mundane tasks such as sorting, paging, sorting,
and deleting data.
2) ASP.NET 2.0 enhances the data-binding architecture, introducing a new
family of components--the data source objects, which act as a bridge
between data-bound controls and ADO.NET objects. The familiar DataGrid
control is still supported, but it doesn't take full advantage of the
specific capabilities of data source components.
You can find more information at here:
#GridView: Move Over DataGrid, There's a New Grid in Town!
http://msdn.microsoft.com/msdnmag/is...4/08/GridView/
In my opinion, if your purpose is to manually load and retrieve data from
cells and controls inside the cells, I would recommend you still use the
DataGrid control, it's still supported in ASP.NET 2.0. If you want to try
the new and powerful data-binding feature of data source objects (such as
SqlDataSource, ObjectDataSource), I would recommend you use the GridView
control.
Hope this helps. Please feel free to post here if anything is unclear.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.