I use ODS when the data will be strictly used for display only. But if that data needs to be manipulated in any way, I stay far away from all of the built in pieces, no grids, no ODS.I think in general, code behind is more useful because it provides a central location for customizing data layer connections.
The dataset provided by custom object datasource allows for easy sorting and paging.
The custom object also provides a central location for data layer access.
Josh E: That depends on your overall speed I guess.
I've gotten to the point now where making a datasource control ends up taking me longer than just banging out the code for the same thing.
At this time, I can not rebuild the application in MVC, so I'm attempting to clean up some spaghetti code in the world of Webforms with constant scope changes and prolonged runtime errors that has layers of bandage. The more and more familiar you become with the underlying ADO.