Hi Josh ---
>
>I would say that saving RAM on the server is an excellent reason to share connections. You could have 200 users using 1 connection each or 20 connections each if you use lots of updateable views. You would see much better performance on the server with 200 connections open than with 4,000.
>
This is true.
>The "connection is busy" error usually occurs because views are not set to fetch all records at once. This causes asynchronous processing of views. Because you can't have more than one command executing simultaneously over one connection, you shouldn't use acynchronous processing with views that share a connection. In my experience, setting the FetchSize of every view that shares a connection to -1 (fetch all) fixes this problem.
>
Hmmm.....I have not had the same experience...it's an interesting fix and I can see where it may help in some cases.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05