>Writing such code is really difficult, debugging it is horrible. I think the average VFP developers are not the right target for this kind of stuff.

Good point. I had only thought about what it would take to put it in the product. I had not thought of the issues the VFP dev would have to deal with. Now that you bring it up, even if multi-threading support is in VFP, I wonder if folks know what they are getting into. You are right, multi-threaded code is a nightmare to debug and test.

>Maybe in the (near?) future computer languages will evolve to the level where multi threaded programming will be a easy and trivial, but now is not the case.

Timing issues and blocking are still going to be problems, unless the languages automagically handle that somehow.

> You benefit from security, transaction support, multi-threading, just-in-time activation and more simply by declaring you whant them. My DLL is far less capable :)

Well, that depends on what your DLL is calling. If it's calling a multi-threaded DLL sitting in MTS/Component Services, then you get all of those benefits.