>
>Ok.... so, what would the advantage of using MSMQ for passing messages? Is this basically for passing messages from Client to Client.... or, from Client to Middle Tier...
>
>Would a mechanisum for an administrator to shut down sessions of my client be one use for MSMQ? I was thinking of using a DBF, but perhaps MSMQ would be a good choice. What is the overhead of MSMQ on a server?
>
>BOb

The nice thing about MSMQ is that it runs as a service, so it's like part of the OS. It guarantees delivery of the message. There are also components that can be placed on different platforms, like IBM mainframes to allow messages to pass between your app and the mainframe. It can also be used at the PC level to pass messages between different apps, for example one in VB and another in VFP. Also, if one of the queue servers goes down, the messages can still be queued on the workstation or another server and will be delivered when the connection is established. I'm just starting to look at MSMQ, but I can see advantages over a table.