>This is the crux of it - Michel wants to use his existing framework object and make it threadsafe with as little change as possible. And the safe way is to instantiate a new object for every hit. Given that I think we're both suggesting the same thing - using a static constructor and static properties for truly global values to reduce the creation overhead...

I have been on it since yesterday afternoon. Basically, the design will be as Rick suggested by breaking down the oProcess functionality of the application object and tieing the application object to oProcess for any hit coming from the Web. So, basically, the application object will be created once. Then, at every page, I will create only the oProcess object which will tie the application object to it by the use of oProcess.oApp.

So, the framework has been adjusted and completed. I need to adjust both applications now. The first one is always done. But, I had to adjust about 4000 lines - thanks for replace all. :)