Bob,

Thanks, I could not use the 'view current connections' because of the login I was using...And the views now work...thanks again!

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