If this is a result of the Confirm page being retrieved from the user's browser cache rather than being refreshed with the new information, you can tell the browser to force a reload of this page every time it is accessed. Look for wwHTTPHeader::AddForceReload in the wc help.

-Rick

>Hard to express and probably missing the obvious.
>User navigates to a page and gets :
>

>Mark the ones you want to cancel and click 'Cancel'
>
>H1
>--- ----
>1 Checkbox
>3 Checkbox
>4 Checkbox
>7 Checkbox
>8 Checkbox
>9 Checkbox
>10 Checkbox
>....
>
>'CancelButton'
>

>User checks 7,9 and CancelButton submits form and this page comes up :
>

>You're about to cancel following pls confirm
>
>H1
>---
>7
>9
>
>'ConfirmButton'
>

>
>Now at this point user navigates to another place by browser buttons, comes back to 'Cancel' page and say unmarks 7, marks 8.
>Then he navigates to 'Confirm' page again via BROWSER buttons. Here sees a confirmation is being asked for items 7,9 not 8,9.
>Is this a stateless world so strict or is there a way to force it change too.
>TIA
>
>BTW I'm currently testing all these with wc shareware and we're gonna buy it in near future. So wc methods are OK (I think I missed one obvious).
>Cetin