>Nick:
>
>Thank you to answer.
>
>My intention is to be able to execute several tasks in unattended mode and each one of them in a different thread; when the same ones finish, they should inform this to the client.
>I know that other alternatives exist to make this; in fact what I need is to make use of the threads from a VFP client; in most of the examples that I read, they do speak of the use of the COM DLL multithreading but from clients like IIS, etc. Is it possible from a normal VFP EXE to create different objects defined in a COM DLL multithreading, but creating each one of them in a different thread? Apparently if a client is not multithread, it cannot create objects in different threads; is this true?
>
>Please, excuses for my English!!
>
>Pablo

Hi Pablo,

I am not sure if I understand correctly what you want to do. Do you want to run several tasks from one VFP client app in multithreaded DLL on a remote server?
I see the problem here in that the VFP client itself is single-threaded. If you call the COM function, the client will wait for return value before another task can be run.
I think you might try to make a workaround by issuing the call to some DLL function from the timer in the client app. (I didn't test this with several calls and I am not sure that you will get the desired result).
Remember that (if) there is just one processor on the server, the total execution time for several tasks in a multithreaded DLL will not be less than if you issue the same tasks in a sequence.