Hmmm. So is it possible to differentiate if the event is firing from a
refresh and not a click?
I noticed that with multiple controls, only the last user event is fired
again on refresh. I tried to "fool" the page by manually raising the event
of another, dummy control, but that didn't work. Is there a way to, after a
control event fires, redirect where the post will happen on a page refresh
without any special user action?
Thanks for all your help,
Paul
"Steve C. Orr [MVP, MCSD]" <(E-Mail Removed)> wrote in message
news:uY9%(E-Mail Removed)...
> You are in the same position with any kind of button control
> The real issue is that a post is done when the user clicks a button, and
> to refresh that page the post must happen again.
>
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://SteveOrr.net
>
>
> "PJ6" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Question about your ConfirmButton control -
>>
>> When the user refreshes the web page after the control has been used, a
>> message pops up, "the page cannot de refershed without resending...", and
>> then no matter what you select (retry or cancel), the
>> ConfirmButton1_Click event fires again. In most cases I would think this
>> behavior wouldn't be acceptable for production use. Is there a way to fix
>> it so that doesn't happen?
>>
>> Paul
>>
>> "Steve C. Orr [MVP, MCSD]" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> I'm glad I was able to help.
>>> Here's more info you may find useful:
>>> http://SteveOrr.net/faq/UserCustom.aspx
>>
>>
>
>