Asp.Net Programming :: Best practice and considerations in choosing source for an <ObjectDataSource>


	Best practice and considerations in choosing source for an <ObjectDataSource> Folks, What are the best practices, pros/cons, performance, scalability considerations in choosing the source/type for an object's ObjectDataSource (consider a GridView that needs to display a SELECT statement from a table external to the website). I have identified several alternatives... 1. Use a custom or pre-built data access class to provide SELECT functions 2. Create DataSets for each SELECT statement, storing them in App_Data 3. Configure a connection to the database through the config wizard "ajmastrean" <ajmastr@gmail.com> wrote in message news:1181140336.367043.30920@g4g2000hsf.googlegroups.com... > What are the best practices, pros/cons, performance, scalability > considerations in choosing the source/type for an object's > ObjectDataSource (consider a GridView that needs to display a SELECT > statement from a table external to the website). > I have identified several alternatives... > 1. Use a custom or pre-built data access class to provide SELECT > functions > 2. Create DataSets for each SELECT statement, storing them in App_Data > 3. Configure a connection to the database through the config wizard IMO, none of them. 4. Use a DAL instead, create a DataSet or SqlDataReader object and do your databinding in code-behind: http://www.microsoft.com/downloads/details.aspx?familyid=f63d1f0a-987... -- http://www.markrae.net