VFP can build Multi-Threaded DLLs, but they will only be true multi-threaded if you host your dlls into COM+. Then your clients can call your server using DCOM or Web service. The client calls will be single-threaded but your server can process any number of client calls at the same time.

>I have a "server" application that receives requests from a number of clients, runs SQL queries or calls remote COM+ objects and then returns the results (currently the queue uses folders and files to communicate but I am switching to IPSocket)
>
>I want to avoid the "server" actioning one long query and ignoring the rest of the queue, I thought about either using "out of process" COM objects for each action in the queue or just calling an .EXE with a parameter EG. RUN /N action.exe /Query2 /Param1 /Param2
>
>The COM object gives me a pointer to the application but I have had bad experience with DCOM, is COM going to work better? Am I over complicating things?
>
>Any ideas or thought welcome!
>
>Gary.