Mike,
>I've been using MM (and business objects) for about a week now. I think I've got my head around some simple concepts, for example, typed DataSets and a business object that works with a single table.
>
>Currently we're creating a DataSet for a single table, then a business object and its methods that return the DataSet. Now I need to flatten some tables (I think anyway), so I can have a convenient DataSet for use in the GUI.
>
>I'm thinking I should create a DataSet containing all the tables and relationships, then the business object's mmBusinessObject.FillDataSet method would use JOIN(s) in its SQL string.
>
>I'm getting a little lost because reading "Establishing Business Object Relationships" in MM .NET Developer's Guide seems to talk about one to many and many to many relationships - now what I need right now.
>
>Hope I'm clear, if not, it's due to sheer ignorance. If anyone can shed some light on the best way to go about this, it'd be much appreciated.
You can do a JOIN in your SQL statement, but you may want to use ADO.NET's DataRelation object instead. Here's an article on the subject:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndive/html/data06132002.aspI highly recommend the book ADO.NET Core Reference:
http://www.amazon.com/exec/obidos/tg/detail/-/0735614237/qid=1072144991//ref=sr_8_xs_ap_i0_xgl14/103-7820263-6487012?v=glance&s=books&n=507846
Kevin McNeish
Eight-Time .NET MVP
VFP and iOS Author, Speaker & Trainer
Oak Leaf Enterprises, Inc.
Chief Architect, MM Framework
http://www.oakleafsd.com