Hi,

Multithreaded compilation server wont solve your problem and make sense only with multi CPU.
check out the Scalability Issues in VFP.

Self destruction of a COM can help you. It should check whether there is any activity from the user and if not, it should run a self destruct code.

Aashish

>Hi,
>
>I compiled my server app as mtdll and I'm using COM+ to access it over the network. When one client failes (and closes itself) it doesn't free component instances it has been using (I can see that from Component Services window).
>
>Now the problem is that when this happens noone can anymore access server components. After having made the call to remote server client just hangs. The only solution I have come up for now is to shut down server application and then again start it.
>
>I guess this kind of behaviour where one client's failure blocks everyone is not very good thing in real life scenario. So are there any solutions to this problem? Could it help if I compiled my server as single-threaded dll not multi-threaded?
>
>Thanks!