On Feb 10, 2010, at 4:42 PM, John wrote:
> Is there another (maybe better) way? I have considered not associating the
> dropdown with a DataField and DataSource and handle the update and save at
> the UI level. But that seemed to violate rule one of the framework.
I would have to understand your data better, but I would guess that
there are a finite number of these combinations, no? If so, I would figure out
a UI method to determine which are shown.
If you disconnect the dropdown from the data binding, an option is to
create a textbox that is bound to the data, and set Visible=False for that. The
UI can then update the Value for that textbox based on the choice made by the
user, or update the dropdown's selected value from the textbox after
navigation. This way you disconnect the dropdown from the data without having
to go to the other extreme you suggest of having the UI manage the data.
-- 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]
