Shut! I really though this will take care of the problem. I'll let you know if I think of something else.

>Hi Hector. This doesn't appear to be working as hoped. I've set the process to low and the thread to IDLE but instead of the COM EXE taking 100% is backs of to 80% but does not let the webserver serve other requests until it is done.
>
>>Evan, inside your COM component you can make a call to the windows API to mark the process as low priority. This will prevent the COM component from using 100% of the processor.
>>
>>Here is the documentation for API function to changes the priority:
>>http://www.news2news.com/vfp/?example=218&function=350
>>
>>You can probably test this before you code it by setting the priority of the COM component to low with the Windows Task Manager and see how it behaves.
>>
>>>Hi folks.
>>>
>>>I have a few reports that are in a COM EXE. I call these from an ASP.NET page and they can take anywhere from 1 to 9 minutes to complete. When the COM component is called it uses the server CPU almost to 100% and doesn't allow other request to the webserver to be served at all. Rick had warned me of this.
>>>
>>>Can I throttle back the process or somehow force the process to backoff when another request comes in?