On Wednesday 10 February 2010 02:04:00 pm Ed Leafe wrote: > 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.
I think what you are saying is to dis-associate the DB field from the selection process. That would eliminate the 'value not in the selection' error. I could create a button to display a list or some other visual clue for selection. But of course I need to display the correct data to the user. So I would not hide the data from the user. But then I need to set the position of the list to match the saved data. Do I - might not? But I'd would still need some way to update() the selection list. Which is what I'm doing now. Hmmmm? So dis-associating the data from the list selection only eliminates the raised error? It sounds like in both cases I request the data from the bizobj. Just at different points in the process. Johnf _______________________________________________ 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]
