I have a web application written in ASP.NET 1.1, but am having problems with users seeing each other's data.

I am not using static variables anywhere, and this problem occurs regardless of whether I set "cookieless" to true or false in web.config. I am using the Session object to store each users data rather than the cache object.

When the application starts the user is prompted to log on. A database connection (SQL or Oracle) is then established (the connection string is always the same).

The problem occurrs when both users perform the same operation at the same time. These involve the execution of a query. It is when the results of the query are displayed in the browser that the problem occurs: user A often sees the query results for user B rather than his own results.

I am opening a connection to the database just before the query is executed, then closing it immediately afterwards. Is it possible that connection pooling is causing this to happen?

Thanks for your help
Gary

Can you give me an example of the query that you are using? It doesn't make sense that user A would see user B's data unless it was reflected in the query.

"The one language all programmers understand is profanity."

An example of the queries are:-

User A: "SELECT * FROM Subjects WHERE GENDER = 'MALE'"
User B: "SELECT * FROM Subjects WHERE GENDER = 'FEMALE'"

These work fine on their own in a single user scenario, but often User B will see User A's results, i.e. results will be all MALE instead of FEMALE.

This is extremely weird and can't say that i have ever encountered this problem. How do you determine what query the users will execute, though sessions?

"The one language all programmers understand is profanity."

Hi,

If ur query should return diffrent data for each user ,Then U must add another condition in where clause

eg. "SELECT * FROM Subjects WHERE GENDER = 'MALE'" and username = session("username")

The user builds up a query using a search criteria form. This definitely works as it has been used by several customers over the past year, but mainly one user at a time until now.

The query is then stored in a Session variable, before being passed to the database to execute.

The user name or session ID have nothing to do with the query results. Any users running the same query should get the same data

No Need to store the query in session object.u can store the query in variable inside the method and exeucte the query directly and check it.

Thanks for your reply but that's irellevant! I need to use a session variable as the query is built up gradually by the user. I'm not a beginner and don't need any help in executing queries - I just need to know why one user get's another user's dataset.

Thank you

Ok lets all sit back, relax, and take a deep breath! Yes, regardless if the query is stored in session or not, that is obviously not the problem nor do I think this is a connection pool issue.

What I find most puzzling is that you are saying that if user A and user B execute their querys at the same time, the result set of query string A gets sent to user B and vice versa.

Is there anything else we should know about this application because, what you are describing, just doesn't seem possible.



"The one language all programmers understand is profanity."

My application is set to cookieless="true" in web.config. I have read that the 24 character session ID generated is not guaranteed to be unique. Is it possible that I have 2 clients with the same session ID. This problem has only happened a couple of times, and all of the application data is stored in Session variables.

Thanks,
Gary