John,

Can you give more details on the problems you've had with views sharing connections? I've worked on several client/server projects using VFP and MS SQL Server and have never had a problem as long as the connection wasn't set for asynchronous execution and the views all had a fetch size of -1.


>>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.