>Personally, I find a single connection held for the duration of the >application session much easier to administer than multiple connections >and this approach has never given me any problems to date. As discussed on the SWANK MS SQL maillist: QUESTION: One of our customer want to use our client/server applciation from about 500 site acroos U.S. This is far more than we ever have experienced. Could anyone confirm or comment the MS SQL server's capability for this case? ANSWER: Will all of the clients be connected at once? This is entirely possible, but will require more RAM (over 18MB) just for the connections-that assumes only one connection per client-which might not be the case. We have seen production rigs that handle far more connections that this. Our rig here on campus runs over 5000 simultaneous users and we have seen larger. What you will need to do is be smart about your connections. When you need one, make it but be prepared for "none available" situations. When you are done, close it-quickly. That means you don't want DAO/Jet to handle this for you. When you run a query pull the rows down quickly and disconnect. This is easy with the ClientBatch cursor library and the batch update mode. I describe these tactics in my book. Bill Vaughn billva@microsoft.com Visual Basic Enterprise Product Manager - Microsoft Corporation Opinions Expressed are my own and not necessarily those of Microsoft Corporation. MAIL LIST INFO: List help: http://www.swynk.com/maillist.asp Searchable list archives: http://www.swynk.com SQL Server FAQ, books: http://www.swynk.com/mssqlfaq.asp Help: contact listmaster@swynk.com Gene Berger The Corner Analyst 13995 Graham Road Pataskala, Ohio 43062 (614) 927-8994 gberger@asacomp.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Displayed using 100% recycled electrons.