>Sir, Thank you very Much. I will try both the things tonight and will also try to GUITHREAD and will respond you.
>
>Thank You
>Regards.
>Harsh


One thing that makes GUITHREAD different, is that it actually launches separate processes for each thread. In that way you will not need multiple ps2pdf.dll copies, but rather each .exe that is launched will attach to its own logical copy of the single ps2pdf.dll file.

Having separate processes can make a big difference in parallel performance, and even ease of programming. GUITHREAD basically provides the "glue" necessary to coordinate message systems between the multiple threads. You basically send it numbers, and those numbers equate to commands, and based on those commands you can do anything. Sending it a particular command, and then another number, might instruct a particular thread to open table foo###.dbf and read the instructions from there, a fully customizable solution using whatever makes sense for your app, and so on.

But, Visual FoxPro itself still uses thread blocking for some things ... even in completely isolated processes. It was never written to be a good multi-thread manager, or parallel execution software. It does work, but it is lacking compared to other implementations due to its single-thread original design.