Gary;

Start up SQL Enterprise Manger. From the main menu Select Server and then Current Activity. On the tab user activity you will, in a treeview, all of the users logged into the system. The activity for each user should be expanded but you can expand it. The information here is Connection Number, Database Name, UserID/ and then some activity, most likely Awaiting Command and then possibly a machine name and the program that is connected. If you right click one of these lines you get a shortcut menu and selecting view details will give you the last SQL statement executed by that connection. The point here is that each line represents a connection. You should see only one line for a particular user (unless you also used that ID for Enterprise Manager!)

You may want to set your default timeout to 30 seconds but you really don't want users waiting too long for data. In my system I also have one remote connection and all of the remote views are defined as using that connection. However it is important that each view be marked as sharing the connection. By definition, they share the VFP connection but the connection meant here is the connection handle or channel for the data. The VFP remote connection definition merely defines how to access the database (connect string, logins, etc) Each view decides if it will share the open channel or open a new one usin the information in the VFP connection to do the connect. So the VFP connection defines the information required for an automatic SQLCONNECT. If views are sharing a connection, they do not have to do a SQLCONNECT once the first view was opened.

Make sure each defined remote view has share connection turned on (advanced options...) This connection is really the data channel that will be used.




>Bob,
>
>I have the enterprise manager utils here to access the server, but I don't see where I can see the actual logins. Can you define that for me...(Appreciate it).
>
>I also checked my remote view defaults under options and its set as shared connection. What should the default timeouts be?
>
>I found an article on M$ that discusses this exact problem of opening and closing connections to rapidly, Article ID: Q170652. I guess if I can figure out how to view those connections I should be able to get this working. Thanks for all the help.
>
>>>In my application I have one (1) remote connection defined. I have "Share Connection" turned on. Up until today I had no problems connecting. After adding a couple of more views I get the error:
>>>
>>>"The maximum number '15' configured user connections are already connected. System administrator can configure to a higher value..."
>>>
>>>That would be fine except it takes a lot of memory per user, and I don't understand why I have 15 open connections (I'm the only one accessing the server). Maybe its because I havent closed a view I'm using after =REQUERY but then again, I guess I don't know how to close a view connection yet maintain the data on the local system. I thought views were automatically closed after the REQUERY command. Am I wrong? Thanks for your help.
>>>
>>>Gary
>>
>>Have you verified in the remote view designer that share connections is set to true? By default this will be false. Also, if you are using SQL Server, you can use Enterprise manager to check server activity and if you look at the details of the multiple connections you have, you can see the actual SQL statement that was last used by the connection. I open up some 20 - 30 views in my application and always only have 2 connections (one for SQL pass-through to use and one that the views open)