Binding to a BO field may be the most basic point but guess which dummy didn't do it?

I really didn't know what I was doing and originally bound to the field and ran the form without realising I had to setup the PopulationDataSourceSettings. It threw an error so I removed the binding and setup the PopulationDataSourceSettings. Of course the drop-down worked but it wasn't bound to the BO.

Now that I have bound to a field, guess what is working now? 10 points to you and a "fail" for me

Well, then you have something else in the mix...this is a very basic control and basic functionality.  I know for a 100% fact that this control follows the editing state of the BO when bound...oh, that would be a 4th point (and the most basic one)

Do you have the control bound to a BO and binding field?

Interesting, I am using a SF combobox and have checked your points:-

1. IgnoreManageReadOnlyState = false

2. ManageUIReadOnlyState = true for both the main form BO and the lookup BO

However, I can open the dropdown and select an item when the form is not in edit mode.

The combobox does follow the EditingState.  The only reason it wouldn't is if:

1. You have the IgnoreReadonlyState property set to True on the ComboBox
2. Have the ManageReadonlyState property set to False on the BO
3. Aren't using an SF combobox.

Sorry, it is still doing it after I have setup the combobox. It looks like the combobox is always enabled regardless of BO.EditingState.

Oops - I spoke too soon. I haven't bound the combobox to a field yet!

I have a test form with textboxes and a combobox. I notice that the combobox is always enabled regardless of the BO.EditingState. Not a big problem as I know it can be handled in our own code, but I think it would be good if all editable controls respected the BO.EditingState.

Thanks.