I have multiple ASP.NET Gridviews on a page, and each has their own Insert/Update/Delete commands.
In order to prevent duplicate DB transactions on page refresh, I am using a Session variable similar to this method here: Example (src: http://aspalliance.com/articleViewer.aspx?aId=687&pId=4)
That works as intended. The problem is that many of our users have multiple tabs open performing actions on different search criteria. If a user runs a transaction on one tab, then switches to another tab, the next transaction they attempt will not commit at all. Since the Session variable has now updated from the other tab, it will prevent the transaction thinking it's a page refresh.
I also cannot redirect to the same URL, as I would lose all search criteria and other form values that need to persist on postback.
Any other tips to have an ASP.NET site running in multiple tabs and also preventing duplicate DB transactions?
