>>>Then he navigates to 'Confirm' page again via BROWSER buttons. Here sees a confirmation is being asked for items 7,9 not 8,9.

Let me see if I understand: you are concerned with what happens if the user goes back and changes the selections on a previously submitted form, and then navigates to the 'Confirm' page without resubmitting the updated form, right? In that case, your array would still contain the old values, wouldn't it, since the GetFormMultiple method would not have been executed against the updated form. And therefore your Confirm page shows the old values even if it gets refreshed (assuming it draws its values from the same array). I don't know how you stop the user from doing this, but that fact that the Confirm page shows the earlier, incorrect values is actually what you would want, isn't it? Because it tells the user what's actually about to happen, even it that's not what they intended.

>Thanks for replying Rick,
>I added AddForceReload() and verified that 'Expires:-1' is in HTTPheader.
>I get checkbox values with :
>
>lncount=Request.GetFormMultiple(@laCancelList,"chkAppt")
>
>Even after a manual refresh lnCount is same and values are old ones.
>Currently I'm thinking if cookies could do it but also afraid not all users could accept cookies (or I misunderstand cookies).
>Cetin
>
>
>
>
>>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