>Hi Sid,
>
>>Slowly but surely.... OK slowly anyway.
>>
>>I know I'm fighting this a little too much!
>>
>>Trying to setup a new web form with a simple MMRad combo box and MMRad text box.
>>
>>I've registered 2 business objects.
>>
>>
>> Protected oClub As New Club
>> Protected oClubData As New Club
>>
>
>You are only registering one business object here and that is what the property builder is picking up. Both of these are the same business object "Club"
>
>>
>>The first object oClub is to drive the combo box, which I have working just fine. Although, when I go to pick the business object from the wizard it only displays 1 object: "Club".
>>
>>
>> bindingsource = "Club"
>> bindingsourcemember = "Clubname"
>>
>
>What are you using to call for data in the oClub business object?
>
>>
>>The second should drive the text box once a selection has been made from the combo. If I set the bindingsource to "Club" I get only the first item name displayed. If I set it to "oClubData" I get nothing.
>
>Are you calling data on the oClubData object? I would suggest just dropping that and doing this slightly different.
>
>You could for instance call:
>DataSet dsClubList = oClub.GetClubList() to fill your combo box then,
>oClub.GetClubById(combo.SelectedValue); to retrieve an entity that is bound to the textbox.
>This is just one way, but remember you are working with a single business object. If you need the combo box data filled and to be persisted, then you might be better off to return a DataSet you can keep it filled with using the Entity to bind to your textbox.
>Tim
>
>>
>>I've been able to get the text box to display the entity.fieldname text by traversing the EntityList.Item(combo.selectedindex) but I think I should be able to do this through the binding properties.
>>
>>How should the textbox bindingsource property and bindingsourcemember be wired?
>>
>>I know the sample passes the PK as a parameter to a new page, but shouldn't this be possible?
>>
>>Thanks,
>>-Sid Meyers.
Tim,
Thanks for the reply. I was just trying to learn the MM Framework a bit and I see what you're saying about the only one object being registered. The whole .NET framework will take a bit of getting used to coming from VFP.
I appreciate your input.
Thanks,
-Sid.