Here's the situation, I have a GridView UserControl that has a custom sort. The sort is custom because our Web Services return arrays of objects, not datasets. We use a StateServer Session State and since the objects have SOAP headers, I can't use Session State or I get a Serialization error.

Here's the problem: When I databind the Gridview, I put the objects in some type of state management. Right now, that's the HttpContext.Current.Cache. Big problem is that I'm having some type of concurrency error in our production environment.

If I sort a Gridview on firstpage.aspx, and someone else is sorting on secondpage.aspx, the datasources seem to converge or replace one another. I'll get an errors revolving around the wrong Object type being set to my own Gridview even though I'm not on secondpage.aspx, I'm on firstpage.aspx.

I've set the Cache object to have a unique ID as in the SessionID, but I'm still running into problems where my sort simply has NOTHING in the object because it was replaced, or I grab another Gridview's object type from another page that another user is accessing.

How can I fix this problem?

________________________
ASP.NET 1.1/2.0 Developer
VB.NET Developer

__________________
________________________
ASP.NET 1.1/2.0 Developer
VB.NET Developer