>>Usually, when we write an application, we connect to a remote datasource when
>>user starts an application and disconnect when user finishes. Otherwise, we'll >get a perfomance problem. Do you think it reasonable to connect just before >updates, deletes, inserts, and queries and disconnect immediately after?
>
>Sure. Why should your server maintain the overhead for a connection that is idle. This is one of the features of MTS, the ability to pool connections. Even if you don't use MTS, there is still a benefit in only connecting when you need to update/fetch data.

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.

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.

BOb