On Jan 10, 2010, at 5:19 PM, Paul McNett wrote:
>> It's not a bug. It's working exactly the way it should. You should
>> either populate the Choices will all existing values first, or not bind to a
>> list-based control in the first place.
>
> A combo box *is* a hybrid text box/list control. I can see the point of
> perhaps
> making a property to control this behavior.
We're not talking about *new* values entered by the user. We're talking
about existing values in the database, but not in the Choices for the control
bound to it.
It's simple enough to grab the distinct values for the column to
populate Choices. For whatever reason, this is not what is being done in this
case.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
