Craig,

A distinction should be made between multithreaded clients and multithreaded servers. With respect to VFP as a client, you are correct - no way to call a method with a NOWAIT clause. However, with a VFP MTDLL server, what Claude and John are saying is correct in that apartment model threading effectively "simulates" true multithreading.

>>Claude was right - what you call it is nothing more than semantics. The fact is, for what Fox developers need - what the MTDLL does - regardless of what you want to call it - fits that need.
>
>John, stop making blanket statements like this. How do you know what I need in my development? Maybe I truely need multithreading.
>
>>Craig - nobody - least of all me - is arguing that Fox is multi-threaded. The fact is - when people say they need multi-threading - they really don't because there are safer - more appropriate alternatives out there. My response to your flawed question was a good example of that.
>
>I agree that there are better alternatives to multithreading...most of the time.
>
>My question wasn't flawed. Your solution may be better some of the time or even most of the time, but not 100% of the time. Your answer to the question totally supported my arguement that an MTDLL is NOT multithreaded.
>
>>
>>Your talking about synch vs. async processing - which is a different concept. For example, eventhough VFP - as a UI client is single-threaded - I can make use of async calls in ADO. It does not do a lot of good unless you are taking advantage of events - since that is the only way you will know when something has completed.
>
>Nope. I'm talking about multithreading, which you are right...it is a different concept than sync vs. async.
>
>>
>>Well, when I did it - my ducks were in a row. The same cannot be said of your argument here. The fact is - from the point of view of the MTDLL - it can process multiple requests at the same time.
>
>It can process multiple requests because it is apartment threaded, not multithreaded. They are, in fact, different animals. They are closely related, but different.
>
>>The MTDLL was created primarily for web-apps. Basically - it is a masterful kludge that was created. Somehow, Calvin managed to weave MT simulation into something that does not support multi-threading.
>
>Calvin was able to do this because of apartment model threading. The VFP MTDLL was designed to be run under MTS, which requires apartment model threading.