>>I don't think you need to clone
>>
>>replace
>>

>>  oProcess.oApp = App.oApp.Clone()
>>

>>
>>by
>>
>>

>>  oProcess.oApp = App.oApp
>>

>>
>>Since this will give you the current reference of oApp
>>
>>
>>The App Class can replace oApp at any time. When it does, oProcess will still hold a reference to the previous oApp
>
>This is what I have been having for four years. The problem is App.oApp is shared. Thus, if a hit in progress is ongoing, and another hit sees that App.oApp.Tables has to be re-initialize, this will affect the first hit, the one that is not finished, and an object reference is not found will occur, if that first hit requires oApp.Tables, for example, at the same time the reset is done by the other hit. As the other hit is doing something like oApp.Tables.Clear and this is why the first hit might be jeopardized.
>
>This is why I decided to clone it. It helps but still not perfect. And, this is why I discovered that cloning is not exactly what it says, thus not a deep copy. This is why I started to look at a deep copy approach but all this is way too much complicated to implement just for the need I have. I believe the Clone support in .NET should have been enhanced to support the cloning of everything under the object or accept a parameter to be able to support it.
>
>Do you understand better my situation? If yes, do you have further recommandations?


Questions

(1) Are we only talking about the App.oApp.Tables

(2) Is App.oApp reinitialized on occasion or not