This is unfortunately one of the side-effects of using server-side
processing in a stateless environment. Nearly every action requires a
round-trip to the server. There's nothing you can really do about it short
of moving all of your logic to the client side and doing a batch update.
Here's the (short and extremely simplified) explanation of why this happens:
1.) User accesses page (page request, 1st history item added)
2.) User clicks "edit" for one of the items in the grid. The form submits
(another page request) so the page can be rerendered using text boxes,
etc... (2nd history item added)
3.) User makes changes and clicks "save." The form submits (another page
request) so the database can be updated and the grid redrawn with the
changes. (3rd history item added)
4.) User clicks "delete." The form is submitted (yet another page request)
so the item can be deleted from the database and the grid can be redrawn
with the changes
5.) ... you probably get the picture by now.
As you can see, each of these actions result in a page request, which causes
the browser to add an item to the history list.
--
Dave Fancher
http://davefancher.blogspot.com
"Bazza Formez" <ba**********@paradise.net.nz> wrote in message
news:aF********************@news02.tsnz.net...
Hi there,
I am *very* new to this... so please excuse poor terminology etc.
I am building a small content management system.. and have just managed to
get an asp.net page up & running that edits / deleted data presented via a
datagrid via a datareader. All is well, the database is updated
correctly..
However after merrily doing a few update cylces, I noticed afterwards that
when I pressed the back button on the browser, I was presented with a
"historical" page for each post cycle. Is there a way to stop this ? I
don't want to see any "history" in this way ...
Is this normal, or is there a setting to prevent this happening ?
Thanks,
Bazza
