Best C# -> SQL calls.... opuinions?

It sounded like in your first post that you said you will be using objects.  If you are creating objects you might as well optimize your app and not use datasets.  If your using objects you can create a generic list of your object.  Generic lists can be bound to almost anything since it inherits from IEnumerable.  Consider the following way for retrieving data.  Create an object that represents a row in the result set you are pulling in.  Next declare a list of the object you created (example List<YourObject> collection = new List<YourObject>()).  Here is the slick and optimized part.  For the object you created, add a constructor to take in a SQLDataReader.  This way you can use the data reader to populate your instance directly in your class.  Now create your sql command linked to your stored proc.  Declare a SQLDataReader, and set the reader equal to sqlCommand.ExecuteReader().  Now you can start your while dr.Read() loop.  While looping you can use some code like this to populate your collection : collection.Add(new YourObject(dr));.  When your done just return the collection.  The function to retreive your data can even be a static function declared within your object to return a collection of that object by whatever parameters.  This way is the opposite of procedural programming, and and centralizes that data in one spot.  This way refactors are much easier.  You wil realize that you can build really sweet data layers similar to linq just by creating your own objects and using generics.  You can also use the linq extension methods on a generic list.  This way might not be the best for your situation, but my way of writing good C# to deal with data.  If you don't believe me look at all the functionality of the generic list class.  This is a different approach than you expected, but datareaders murder datatables when pulling in data. I am only telling you all this since your from NJ!

Okay I won't OSTRASIZE you.  You sure can bind generic lists to repeaters.  The best part about binding to a repeater is that on the item created event you can access the dataitem.  The dataitem will be an instance of your object for the databound row!  Let me know if you have more questions.