Hi Lynda,

You're not the first person to use shared connections for the views. The problem you have indicates that something is not configured properly either on connection or view level.
Using a connection string will create new connection for each view which could be expensive. It'll also use more SQL Server resources. If SQL Server is licensed per connection, you can easily exceed the limit.
Check also http://blogs.msdn.com/khen1234/archive/2005/10/18/482202.aspx

>After more than a week of work, I can't eliminate the Connection Busy messages so must assume that opening multiple remote views with the same handle is a bad idea. I am willing to switch back to the connection string and forego the performance boost, just to get the app working again. However, what problems are likely to be encountered when obtaining a new statement handle for each view?