>The real problem is you're trying to do something that VFP COM objects really aren't suited to well; you'd be much better off writing the COM component in an event-driven mode, but VFP doesn't have an easy way to idle without eating the CPU alive or passing control back to foxisapi. I'd really look at a major redesign, since VFP isn't really a platform well-suited to this type of problem.

Exactly my feelings.
Too bad I gotta finish this for tomorrow. I'll take the other road I had which was a "semaphore" driven exe which will take care of the Winsock control and it's job where I can use READ EVENTS. The COM dll will put a semaphore file with the data to be processed and return. The obvious problem being that I will not know if the job was done.

I used to do it like that with VFP3. There was a way to run the exe as a NT service but I can't remember now.

Another approach I might look into is using CreateProcess() to run a exe that will take care of the job and using WaitForSingleObject() to wait for the exe to complete the job, this way I'll know if the job was completed or not.

Anyway, thanks for all the help.