Hi Vlad,

Thanks for taking time out to respond. Let me take a moment to describe my situation.

I am in charge of redesigning a LARGE VFP 6 application to move from FoxPro database backend to a SQL Server 2000 backend. I have been able to make the following changes across my application.

1. All forms are Remote View based. (I use SPT for non-visual work)
2. All Views are set to NODATA on Load.
3. All Views are parameter driven as to reduce the amount of data to only the necessary records.

I can set all the Remote Views to Share Connection. I haven't done so yet for 2 reasons.
1. The system was working when I didn't share the connection. (I had tried sharing one before but the Connection is busy error popped up everywhere.)
2. I wasn't sure if every connection correlated to a SQL Server seat, which correlates to money! This is BAD! :)

What I would like to see explained:

If I open all the views in my form with NODATA on load, and make sure that they are all have Share Connection set to True, what else would I need to do to make sure I do not see the Connection is busy error?

Also you mentioned sending the "use" command to SQL Server to swap databases to get around the build in connection of the remote view. Could you sample this as well?

TIA

-- Chris