Magic Trick Datagrid Delete Row

[Shawn]

I have found many cases in that after a row has been deleted from a datagrid
using a linkbutton and then hit the browser refresh button the row previous
to the origianal delete will as well be removed if there is one. I have
attempted to track the refresh in a session variable, but in all honesty
would like to disable the refresh button/F5 on ie.
Any thoughts

[Brock Allen]

This is how the browser works. If you hit refresh you're asking the browser
to do what it just did. If that's a post, it warns you but you're sentiment
is correct, since no one reads or understands the warning. The best way to
avoid the user refreshing and reposting is to Response.Redirect(Request.Path)
which causes a GET. Then a refresh is just another GET of the page.

-Brock
DevelopMentor
http://staff.develop.com/ballen

I have found many cases in that after a row has been deleted from a
datagrid
using a linkbutton and then hit the browser refresh button the row
previous
to the origianal delete will as well be removed if there is one. I
have
attempted to track the refresh in a session variable, but in all
honesty
would like to disable the refresh button/F5 on ie.
Any thoughts

[Shawn]

So, how do I change that one control to get. If i changed the form attribute
the rest of my controls will not work? I am an entrylevel programmer and use
vs.net to create event handlers.

c#dev

"Brock Allen" wrote:

This is how the browser works. If you hit refresh you're asking the browser
to do what it just did. If that's a post, it warns you but you're sentiment
is correct, since no one reads or understands the warning. The best way to
avoid the user refreshing and reposting is to Response.Redirect(Request.Path)
which causes a GET. Then a refresh is just another GET of the page.

-Brock
DevelopMentor
http://staff.develop.com/ballen

I have found many cases in that after a row has been deleted from a
datagrid
using a linkbutton and then hit the browser refresh button the row
previous
to the origianal delete will as well be removed if there is one. I
have
attempted to track the refresh in a session variable, but in all
honesty
would like to disable the refresh button/F5 on ie.
Any thoughts

[Shawn]

I am sorry, I read your reply to fast(hopefully a bigginer thing) but that
worked great thank you so much!!!!

c#dev

"Brock Allen" wrote:

This is how the browser works. If you hit refresh you're asking the browser
to do what it just did. If that's a post, it warns you but you're sentiment
is correct, since no one reads or understands the warning. The best way to
avoid the user refreshing and reposting is to Response.Redirect(Request.Path)
which causes a GET. Then a refresh is just another GET of the page.

-Brock
DevelopMentor
http://staff.develop.com/ballen

I have found many cases in that after a row has been deleted from a
datagrid
using a linkbutton and then hit the browser refresh button the row
previous
to the origianal delete will as well be removed if there is one. I
have
attempted to track the refresh in a session variable, but in all
honesty
would like to disable the refresh button/F5 on ie.
Any thoughts