>>VFP’s thread management or lack thereof is hardly germane to the query at hand.
>
>Huh? Of course it is.

Yep! There seems to be some confusion here to the difference between a process and a thread. So if you'll allow me...< s >

Processes basically run in their own address space, regardless of whether or not they're Free or Apartment model threaded. However, a process that's free threaded does not need to spawn additional instances of itself to handle multiple requests from the OS. VFP is Apartment modeled (including, BTW, MTDLLs). If the OS runs multiple copies of the same VFP process, they'll be run separately, in their own address space (MTDLLs excluded). However, if the OS requests something from a Free threaded DLL or application, it may not be re-loaded. An example of this is SQL Server. It supports both threading models, so it may run in either manner. The information on how the OS handles this is stored in the registry.

MTDLLs are the exception since a Free threaded intermediary is required, such as Foxisapi. This is what handles the marshalling/unmarshalling issues.

Win32 is a pre-emptive multi-tasking OS as you know. Applications can't tell the OS to do anything, much less processor allocations. The best any app can hope for is that the OS will grant its request. IOW, the OS is the dog and the application the tail, and the tail wags when the dog tells it to. No more, no less.

May Ed and I should write that book.< vbg >