Mmmm...
Maybe I'm wrong or I'm missing something, but some weeks ago I face a
similar problem, and it seems that cascading drop down is not prepared for
"update mode".
Possible solutions:
- Implement the out of bounds calls simulating that a client is selecting
the right option (you should first place a javascript method to be fired when
the page is loaded on the browser, and then go capturing the outofbound
calls).
- Extend the Toolkit control to allow "update mode".
- Use another login for the cascading (build up your own methods to
update, maybe via webservices, or altough is not very optimal, using update
panels).
If somebody knows a better solution, please giveme a shout :-)
Good luck
Braulio
/// ------------------------------
/// Braulio DÃ*ez
///
///
http://www.tipsdotnet.com
/// ------------------------------
"Gary L" wrote:
I've implemented a cascadingdropdown modeling the examples found on the web
and that work fine on an initial data entry screen. What I can't seem to
find an example of is after I've stored data and want to come back to the
screen for editing how can I get the lists to populate and set the
appropriate value? Any examples out there that I'm just not finding?
Thanks!