>If oApp is a property of the application I don't see how the old instance would be affected by the creation of the new instance unless the new one locks (or attempts to lock) some *external* resource which might still be in use by the old.....)

In my App.vb file, I have this definition:

        Public Shared oApp As Framework.App = New Framework.App()

Across the entire framework and application, oApp is visible. Framework is the namespace. The only locking happens during the loading of the data dictionary by the first hit who gets there first. When finished, the hit unlock the process. Since I adjusted to that recently, this has resolved the issue that only one hit could load the data dictionary into oApp.Tables and then set, at the end, oApp.lTables to True telling everywhere that we are done.

So, basically, if oApp is Shared, even if an application recycles, you are saying that the new oApp should not be effective to the old hit as the old hit still has its own oApp private that that IIS cycle. Is that correct?