To flesh Paul's point out a little the problem is that VFP COM components don't support multiple simultaneous calls to the same method when registered under MTS. This of course was one of Microsoft's major selling points for MTS. No worries about multi-threading. Just code it single user and go! But if more than one user calls a VFP COM method at the same time, the method calls get queued up and are handled sequentially. The VFP folks at MS are supposed to be fixing this but when we'll see it is anybody's guess.
Now for the "but". But, if you do register the component with MTS and you're using ODBC to connect to data, you could take advantage of MTS's connection pooling.
So you'll have to evaluate the trade-off of method call performance vs. resource consumption by multiple instances of your component.
>There is no advantage in using a VFP dll with MTS (because of some problems between these two). Wait until these problems will be solved.
>
>Vlad
>
>>I make VFP .dll for ASP component.
>>it works very well, ( sometimes it seems to be very slow - Because it needs overheading time ) but someone says me that regist my dll to MTS.
>>But I don't know why I must my dll regist to MTS.
>>only using Regsvr32 and regstering then I manage web site.
>>It seems work well.
>>
>>Does anybody can give me a answer?
>>thanks.
>>regardings
>>
>>Lee.
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
