>We have SQLServer 2000 which we are using with the Client Access License. Recently more and more users are getting errors saying that the Connection Handle is Invalid or the Connection failed. Some of these errors are occurring on programs that haven't been altered in over a year. We are accessing the server from Visual FoxPro using SQLstringconnect() with a user name and password. We cannot use trusted connections because part of our network is still Novell. Some programs may access several databases on the same server. I have a separate connection number for each database because as far as I know there is no way to connect to the server and then use the connection for different databases.
>
>My questions are
>
>1) Can one SQLstringConnect statement be used to access several different databases eliminating multiple connections?

Yes. Do a SQLEXEC() and do a "USE databasename" to switch to another.

>
>2) Does each SQLstringconnect count as one seat on the license, so if a program connects to 3 databases it is using 3 access licenses?
>
>3) Does VFP have a way to capture the fact that this is a license error and not a connection error caused by other problems on the network?
>
>4) If the server is running out of licenses could that also cause a time out on queries?
>


Sorry, no help on the others.