Hi
We have an ASP.NET 2.0 application which uses the old Enterprise Library Data Access Block (SqlHelper) to get SqlDataReader objects from the database and populates a list of objects.
When multiple users logon to the site - the connections are getting mixed up. When User A logs on and requests for a page which runs query A - he sometimes gets query B results (which resulted in due to User B's request).
When we turn off the connection pooling via connection string - the problem seems to go away.
Anyone has seen this before? Any potential resolutions?
Thanks
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com