>Im wondering whether you guys prefer to bind collection of custom objects to the grid and other list controls or use datasets. My pain with the first approach is that I have to write tons of code to enable sorting, searching and the custom pagination. THe advantage is that once i bring the collection (as needed per page size)of objects to the client, I can cache the objects and can retrive them later if the user goes into details.
>The other approach is to get a recordset, bind it and on selection to load the custom object from db.
>Pros /cons? Im trying to go 100% oop but I may have to throw in some built in featuers of the .net datasets.
>
>Looking for your input.
>Thanks,
>Vlad

Vlad,
I started with object but had some of the pains that you mentioned. I switched to datasets and followed some of the great design tips given by Bonnie over the last few weeks. If you browse some of her messages you should be able to find what you are looking for.

Yesterday I found a few good articles on CodeProject that really helped explain custom objects. The focus of the articles were to use customer objects efficiently with ADO.NET. Here are the articles:

http://www.codeproject.com/dotnet/ADONETOOPPart3.asp

(That is the third article, but has links to parts 1 and 2 at the beginning)