No. Setting Asynchronous to .F. simple means that the application waits for the result set to be returned before continuing. In the case of sharing connections, this means that only one SQL process will be using the connection at one time, avoiding the dreaded "Busy" message.

>>No...I mean the opposite. Try setting it to synchronous (the default is asynchronous) and leave share connections on...warning, though, it's gonna get slow in some cases.
>>
>
>I'm confused. You said that I can achieve the best performance with Share Connections OFF. In order to do so, I think I should have the connection synchronous so the connections are used one by one and the maximun number of connections used is the number of RViews I have open at some time. What am I missing?
>
>TIA
>
>>>>Hi Victor,
>>>>
>>>>It could be a combination of settings. If multiple tables are being opened via the same connection and it's an asynchronous connection, you might run into this error. Why do you have share connections set? Is there a resource issue...the best performance and the least hassle will be to leave share connections OFF.
>>>>
>>>
>>>When I have Shareconnections OFF I run out of connections very quickly. Do you mean that it'd be better to have the connection synchronous and share connections OFF?