>Jim,
>>Can someone specify just what it IS that IS delivered in VFP 6 as far as MTS is concerned along with their understanding of just HOW that will prove to be helpful in solving *present* difficulties?
>
>I haven't tested this but have heard from several people (Randy Brown from MS and Rick Strahl from West Wind for starters) that when multiple clients are accessing instances of the same VFP component running under MTS, only one client's request will be processed at a time. This means that if your object x has a method called y that takes 1-20 seconds to run and both client a and client b execute z=x.y() at about the same time, the second client to make the request will have to wait until the first client's request is fulfilled. This is obviously quite bad if the first request takes 20 seconds and the second one takes 1. Microsoft suggests having several instances of you components running under MTS, but then you'll have to deal will the pool management yourself and you'll lose some of the benifits of MTS.
>
>What's new in VFP 6 is that in VFP 5 only one client can have an instance of a single VFP 5 COM object at once. That means that VFP COM objects can't practically use MTS at all. Mainly what this will help with is creating middle tier components when using SQL Server as a back end.


George Goley spoke on this at Tech Ed. He said they had tested systems with over 130 instances of VFP running and the performance was fine. Pretty amazing huh?

John Harvey