>Hi David.
>
>Long time no chat!

I've got to make it a habit of dropping every once in a while, you know...

>>I have only one comment to this thread - rather than set up timer-based COM objects and arcane API calls, wouldn't it be easier to just switch to Unix/Linux? One statement in most languages, and there you are - a forked child process.
>
>Since this is a VFP issue, that wouldn't work.

True. I'd just like to see ways to fork independent processes in the Microsoft arena in a relatively painless way, though. That would make the question a bit easier to deal with. Call it a native distrust of the Timer class on my part.

>An alternative to timer-based COM objects, BTW, is using COM+ to manage the object pool.

Haven't delved into that yet. Having said that, I'm currently working on a rewrite of DupCheck (which I will be posting up here) that involves a VFP COM object to do the back end work, and a separate VFP front end for the user interface. There are lots of advantages to that, though I've found some bugs in VFP 6 that makes passing arrays to and from a COM object quite interesting. More when I post the final product...