Oh now that's a big help in understanding how to resolve your issue. That explanation in the Docs needs some help of its own. What kind of explanation is

"If you specify a connection as shareable by setting lShared to True (.T.), you can share the connection later by calling SQLCONNECT( ) and passing the numeric value of the connection handle as the first parameter. For more information, see SQLCONNECT( ) Function."

For those of you reading along, here is how I read that statement:

If I specify a connection as sharable by setting lShared to TRUE in my SQLSTRINGCONNECT function, I can only share that connection LATER by calling SQLCONNECT passing that handle and thereby creating a NEW handle that is now truly sharable.

Holy crap, how convoluted is that?

>Hi Mark,
>
>Doesn't make sense to me, either. But that seems to be the way it works.
>
>BOb provided the answer on F1 Technologies VFE Forum. Here is the text of his message:
>
>"I argued about this in the beta and they just didn't listen to me. This is from the Doc, it might help:
>
>SQLSTRINGCONNECT( ) always creates a new connection when it successfully makes a connection. However, setting the lShared parameter determines whether you can share the connection later. If you specify a connection as shareable by setting lShared to True (.T.), you can share the connection later by calling SQLCONNECT( ) and passing the numeric value of the connection handle as the first parameter. For more information, see SQLCONNECT( ) Function.
>
>You can use SQLCONNECT( ) to obtain a new statement handle on a shared connection that was opened using SQLSTRINGCONNECT( )."
>
>Regards,