>>>Hi All:
>>>
>>>This is my understanding of VFP multithreading. Comments are appreciated.
>>>
>>>VFP handles multiple threads of operation by creating an apartment containing all the objects created on that thread. It cannot process multiple threads simultaneously, instead, it switches from thread to thread in a time sliced fashion. This gives the illusion of mutlithreading.
>>>
>>>To realize the performance gains of multi-threading you need a multiprocessor machine.
>>
>>Any CPU can handle only one task at a time and must use time slicing to handle multiple tasks. IOW, it's not a VFP limitation, it's a CPU limitation. I have no first-hand experience with multiple processors, but have heard horror stories from those who have.
>
>Not necessarily. You may have a thread which does some disk/floppy/other HW operation, and these may use little processor time, so if it happens in a separate thread, the original thread may keep singing almost undisturbed. It doesn't have to wait for the HW issues to get done, so there's still some gain.

You're correct on this point. I may have misinterpretted the original question somewhat. And I think others have misinterpretted what I was trying to say. I interpretted the question to be whether or not time slicing was occuring. My response was that when multiple tasks required CPU time, there was always some time slicing that had to occur. (Well, except in cases where a process won't give up the CPU, but that isn't multitasking, now, it is?)