Michel,

Do you have any shared properties or methods in your Framework.Framework.Data class? This could cause these kinds of problems.

~~Bonnie


>>Great!
>
>Well, believe it or not, I still have the problem. The global properties are ok. That part is resolved. But, recently, as I got more and more hits, I found that I was receiving all kinds of errors I was not able to explain. Those are all related to the data provider class. There must be one simple thing that need to be adjusted in there. Here is what happens. If two users access the site at the same time, the data provider of each process is mixed up. This is similar to the original situation. However, it only happens in a specific class.
>
>When the application starts, oApp is created. That is the global application object. Then, at every hit, oProcess is created. So, oProcess only lives at the hit instance and only for the specific user. But, when a hit needs to have access to the data provider class, if another hit is coming at the same time, I may run into an error. Here is how I create an instance of the class:
>
>

>        Dim loDataProvider As Framework.Framework.Data = New Framework.Framework.Data(oProcess)
>

>
>This seems to be clean for me but I guess it is not. loDataProvider is local to the aspx page. So, how come it could get mixed with another hit coming in? This is a mystery for me. Isn't it the proper way of creating an instance of a class?