Matt,

>I'm still digging into the basics of MM and BOs. I hope everyone can suffer through my newbie questions...
>
>Ok, some basics here about binding listbox/combobox to a BO...
>
>Why do you assign a BO in the BindingSource property, but when you assign the BindingSourceDisplaySource and BindingSourceValueMember, you are given the "MM .NET Binding Source Member Selection dialog" where you pick a table and column from some selected SQL database. I would expect to only be able to choose one of the property fields from the EntityObject of the BO that I specified.
>
>Then the same thing happens when assigning the BindingValueSource and BindingValueSourceMember... You assign a BO to BindingValueSource, but then when assigning the BindingValueSourceMember, instead of picking a property from the destination BO Entity, I am again offered the "MM .NET Binding Source Member Selection dialog" from where I choose from any table and column in whatever database I choose.
>
>If I can point directly to tables and columns from any database, why do I need to point to a specific BOs? Or, said another way, if I assign BOs, why do I get to pick from any table and any column in any databse, when then BO only has certin properties in the BO entity?

This again is an MM .NET 2.4 convention. Although you *can* bind directly to entity properties with MM .NET 2.4 all of our documentation currently has you binding to the underlying data table--this changes in MM .NET 2.5. When you are specifying the BindingSourceDisplayMember and BindingSourceValueMember you are not actually specifying database column names. you are specifying column names of the data you are retrieving in your business object (which is often the same, but not necessarily). I think all your confusion will be cleared up in MM .NET 2.5 when you bind directly to the properties rather than the underlying data.

Best Regards,