>I believe becuase as you said, the processing of connecting takes time. And, or course, MTS maintains the pool of connections and doles them out to object that need them, it doesn't disconnect and reconnect every time something needs a connection.
>

Yes, but that is MTS, not your app maintaining the connection. And, there is not a one for one correspondence between the connections in the pool and the number of clients that could potentially connect at the same time. Connection pooling represents a hybrid situation in that you get the advantages of preserving connections and the speed (or close to it) of having the connection around.

>That is why my initial post of this thread wondered what 5 users ment... did it mean 5 connections, 5 concurent queries, etc? One badly designed application written in Access in our company uses up to 10 connections per users to the SQL server.

I am sure it means 5 concurrent connections.