You are keeping some sort of index for each page you are displaying I'm
sure (it gives you the "page 3 of 10" notion).
And...you are no-doubt passing this index when the form you describe is
submitted (so that you can display the "next" set properly). So...that
means that everytime the form is submitted you know both 1.) the set of
possible checked values and 2.) the set of actually checked values.
Your routine can always (in this order) remove the entire displayed set
from your list of checked items and then add those that are checked.
- Ben
Stephen Adams wrote:
Hi,
In the application I'm writing the user can page through a resultset.
I have stored the results set in a session variables so that it is
available when the page reloads (displaying the next page). As the
user goes through these pages they can check a number of checkboxes as
they go. The value for these check boxes are added to a structure
again stored in the session scope so its available after the page
reloads.
The problem I'm having is if the user goes back a page and unchecks
some checkboxes then goes forward to the next page how can I remove
from the session structure the uncheck values.
I do have one idea, every time the page is loaded I can compare the
existing structures values against what has been passed by the
submitted form and removing the values that are in the session
structure that are not in form, but I'm not sure this will work as I
hope.
Has anyone else done something like this?
Stephen
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject
of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]