>>The two instances overlap. The original one will still complete the processing of any current hits before shutting down.
>>But you will lose session state on existing sessions (unless you are using SQL or state server)......
>
>I think this way of doing things conflicts with my current infrastructure. Basically, when the application starts, I load the data dictionary in memory. While doing this process, all concurrent hits are locked. We discussed that recently. This works well. Then, when the hit that got the data dictionary loading responsability finishes, a oApp.lTables property becomes True. This means we are ready to process as usual.
>
>Now, when the application recycles, I do not have any control on that. So, the hit in progress, those that are already running when the new hit falls into the application recycles, will use oApp.Tables collection as usual but might fall into the situation that oApp.Tables is being recontructed by the hit which will be the first one into the new cycling. So, basically, the concurrent hit, the one using the old cycling, will do several SQLs and one of them will generate an error, if it happens during the time the new hit doing the reload will initialize the oApp.Tables collection.
>
>oApp is a share object. So, how can I resolve that issue?

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.....)