You might want to re-present the problem. When I read your email, it seemed like you were describing a typical use-case:
1. Get data from a persistent store
2. Populate form. If attribute indicates "selected", preselect checkbox
3. Render form (allowing user to edit)
4. Persist edits.
Dennis
| "Chris Cranford"
<[EMAIL PROTECTED]>
06/16/2004 03:35 PM
|
|
I haven't seen any comments on this .. any ideas?
> To broaden the prior discussion on resultset caching, I'd like to also
ping
> the group on the concept of being able to have this "resultset" of data
and
> paging through it but extendeding it to where a checkbox exists for each
> viewable record. I need to be able to pre-select values from a database
> ahead of time based on past settings and permit them to page through the
> resultset setting all their new values to finally accepting those and
> writing them back to the database when the user hits the "Save" button.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
