With any programming language, with a single processor machine, only 1 thread can run at a time and thread switches occur in a time-sliced fashion to allow the illusion of multiple simultaneous threads. With an n processor machine, with n > 1, n threads can run simultaneously. On a multi-processor machine, multiple simultaneous threads can be servicing client requests. IOW, throughput will be much greater, minimizing bottlenecks in the processing. VFP mtdlls, in addition to other multi-threaded applications, can take full advantage of this.
I'm not sure if .NET would manage instances in this case or still MTS/COM+. You always need the vfp8t.dll when running a vfp mtdll...

>Suppose I have an ASP.NET web app that uses VFP8 MultiThreaded COM Servers to do most of the hard work producing tables to support Crystal .NET reports. (Local VFP data)
>
>Q. My client would like to know if buying a multiple CPU Web Server will make processing requests faster. If so, how so?
>
>Q. Will .NET manage instances of the COM component classes to use any available processor time regardless of which physical CPU is available?
>
>Q. Is it necessary to use the vfp8t.dll if .NET is managing my interop class instances?
>
>Any other comment would be welcome.