Both MSMQ and Queued Components work asynchronously. For example, the workstation will send the message and then go on with other work. It doesn't care about what happens to the message. Another component, typically running on a server then reads the message and processes it.


>Thanks Craig,
>
>I am reading your MSDN/Foxtalk articles now.
>
>I did find a thread here (UT) where you stated:
>
>"You have to use COM+ Events and Queued Components in situations where you don't care about getting a return value. For example, you could spin off a lengthy report process and then email the results or have the user come back later. If the return value is important to you, don't use COM+ Events or Queued Components."
>
>My initial response is that I DO need a response because I need the balance buit I am probably misunderstanding.
>
>I understand so little but I will get there.
>
>Thanks,
>John