>>>Not possible.
>>>
>>>You want to do it that way because the process takes a long time ?
>>
>>Yes, several minutes if the user is running for a large dataset. They want the user to be able to get live updates on the progress while the component is running but at the same time allow them to navigate away to another page. Either way, I'm supposed to redirect the browser while the component is running.
>
>
>Ok, this is the way I would do it:
>
>Your ASP page that start the process would only set a flag in a database.
>An app running on the server as an EXE or better, as a service would poll the database, start the long process and update the flag table.
>Your "status" page would hit the flag table and can display the status to the user.
>
>This way, your ASP pages are never tied up with long process and your application can scale:
>1-If your process eat to much CPU, you can move it to it's own PC.
>2-That way, you can serve a Web farm.

Hmmm. Sounds interesting.

Why don't I just implement my component as a queued component and have MSMQ handle the firing of the method?

Have you worked with MSMQ or queued components? Do I need to write a scheduler or some kind of timed process that queries the queue?

Thanks,

-JT