That's a good question. I think only your own testing will tell. You probably don't want to totally rule out MSMQ yet either ....
>GREAT!
>
>I really hate to keep asking so many questions.
>
>It will take a day or 2 to figure out or at least get familiar enough with this to incorporate it into my app.
>
>Before I do that I should be as sure as possible that it will fulfill my requirements. It is a little more complex than I first stated as I was trying to just get the basics.
>
>I have an EXE that is run on the WS's. There are multiple WS's asking for account balances simultaneously.
>
>In fact within the app (that is running on the WS), each WS could ask for 2 different account balances at any point in time. In addition there is a function within the app that saves sales data and each instance of the app (each WS), can be doing 2 of these at any point in time. Never more than 2 but it could be asking for 2 account balances or 1 account balance and trying to save a different account's sales transactions, etc. Basically I have a touchscreen Point-of-Sale app with a split screen and 2 users selling to 2 people simultaneously. The whole point is to not hold the LEFT side up while the RIGHT side is asking for an account balance or saving the sales transactions, etc.
>
>Will the basic principles here work? I am worried about the server app being able to handle multiple requests from the same or multiple WS's. The server app does not have to process them simultaneously. It just has to be able to handle receiving them and returning the results as they are available.
>
>Thanks for all your assistance,
>John