>>Unless you do something to specifically prevent the operating system from gaining control (such as setting the priority class of a process to real-time, and then never do anything to retrun control to the OS kernel), Windows is always 'multitasking'...
>
>I agree, and wasn't disputing this fact. I was just trying to clarify something for Charlie in the original message, which indicated that he thought it was VFP that was causing multiple threads to use "timeslicing", and not something inherent in the way multiprocessing works.
>

You're right on the money there; VFP isn't directly managing the CPU resource at all. It's letting the operating system do that for it. What we've gained with SP3 and the MTDLL from what I can see is for a single VFP session to start multiple threads of execution within a single instance of VFP (as Rick pointed out, there is some global code, but each thread uses its own local storage for each instance so that things in different threads don't stomp on each other. Rick summarized my own misunderstanding and corrected it very neatly earlier in this message thread.)