>Hi All,
>
>I'd like to see if anyone has tried something like this before and if they'd care to share any experience.
>
>I've got a scan loop that does some fairly heavy processing, using an activeX control, which is taking about .1 seconds for each pass. I'm up to 60 records, which is starting to seem a little slow to end users. I've optimized the code as much as I can at this point.
>
>What I'm considering is a kind of multi-threaded approach in which I would create several VFP COM servers that split up the SCAN between them. IOW, the first would scan records 1 through 20, the next 21-40 and so on. The COM servers would then return their results to a shared table and set a flag in the main thread controller program to notify when they've completed.
>
>Reasonable? Will there be a measurable performance gain? Pitfalls?
>
>Thanks,
>
>-Matt

Are the different COM servers supposed to run on the same machine or on different machines? If they are on the same machine, are they going to run on the same CPU?

'cause if they run on the same CPU, it will not take less time in total, but rather more. The advantage of multithreading is not that time is saved in total, but that the user can continue doing something different while waiting.