My preference is also to use a strongly-typed dataset if you use a dataset. It's better to let the compiler catch a syntax error than to wait at run-time.

BTW, I also prefer the business objects way than datasets. IMHO, DataSet are often way to heavy for my needs and you're stuck in the .NET world. If you later need to interact with a .NET layer that expose DataSet and you don't use a .NET tool, then you're pretty much stuck.

>My understanding is that if you use DataSets, the preference is to use a Strongly-Typed DataSet which would set your structure in stone similar to a business object. Also, my business objects are fairly complex so I'm not sure what you meant by that statement.