>MTDLLs aren't truly multi-threaded. They are STA threaded components and COM calls them from different threads and isolates the threads providing a simulation of multi-threading. THis is why you can't create multi-threaded code from VFP directly - you need a multi-threaded COM client calling into VFP to provide this functinality.

I note when I look at my Task Manager - there are a bunch of SVCHOST running - some using a lot of memory and some using less. Would multiple requests for a VFP MTDLL also show multiple VFP instances in the task manager with varying degrees of memory consumption?

It almost seems that STA's - even on the "user's" desktop are the norm. XP seems to do a more efficient job of loading and managing them than earlier versions.

So why did MS promote the VFP MTDLL if it is so "useless"? There has to be a reason beyond marketing something that "isn't" to us muggles behind the benches.