>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.

That's a common misconception. Heavy how? Across the wire? You don't send the DataSet across a Web Service, you send MyDataSet.GetXml(). It's not as heavy as the DataSet itself (no schema gets sent and only the actual data that is present gets sent). Plus, it's only a string of XML. Anything can consume it, not just the .NET world.

~~Bonnie



>
>>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.