On Wednesday 10 February 2010 12:05:03 pm Ed Leafe wrote: > If I had data that varied with every single call to update(), I sure > wouldn't be using a dropdown list.
But I do and what would you use instead? The dropdown choices and keys change with change of a child. So I have Parent ->children. Each child has associated allowed data. So I use the dropdown to allow selection. The children are on a grid. You can have many children. Each child has associated data. So the children are the parents of the associated data. Actual case: I have a student that has many enrollments. Each enrollment will include a course, a location, a referring court and each court may have many probation officers but only one may be selected. So to select the court I have a static list. But to select a probation officer I need a dynamic list that depends on the court selected. So I used a dropdown to list the probation officers. The user selects an enrollment from the grid (this act calls update) the associated data must change. That means the Choices and Keys must change for probation officers dropdown. If it does not change the 'value not in the selection' error will raise because I saved the key value to the DB. 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. 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]
