In a great deal of sample code, including the quick start, databinding is done declaratively with a data source object on the page and the DataSourceID property set to the data source. In simple databinding scenarios, the DataSource property is set in code and the DataBind method is called. However, if you want to use advanced capabilities such as sorting, filtering, paging or CRUD actions then the simple databinding falls apart. Then comes advanced databinding, wiring up the OnNeedDataSource event with the DataSource property. I've been able to get this to work but I've found that I can no longer call Page.DataBind without various bad side effects happening in my grid. Other controls on the page need to be databound. How does one resolve the two techniques, especially if the grid is in a user control and other controls on the page must be bound using the binding syntax (<%# %>)?
Thanks,
Kevin
Thanks,
Kevin