We are running a VB program (3rd party) that accesses SQL7.
How do we control what network protocol is used to access SQL? (ie. tcp,
named pipes, etc.).
Do we have to install and run the SQL client network utility on each PC?
Thanks,
We are running a VB program (3rd party) that accesses SQL7.
How do we control what network protocol is used to access SQL? (ie. tcp,
named pipes, etc.).
Do we have to install and run the SQL client network utility on each PC?
Thanks,
Quote:> We are running a VB program (3rd party) that accesses SQL7.
> How do we control what network protocol is used to access SQL? (ie. tcp,
> named pipes, etc.).
> Do we have to install and run the SQL client network utility on each PC?
> Thanks,
Paul,
If you are connecting with the ODBC driver, you can also create a DSN to
define the connection. When configuring the DSN you have the option to
specify the client network library. If you wanted to do it as a DSNless
conenction, create the DSN as a file DSN, open the file that is generated,
and semi-colon delimit the parms in it to make your connection string.
Having said all that, Carlo's link from to the KB article really spells it
out for you. It is probably a little more straight-forward.
Bret Stateham
http://support.microsoft.com/support/kb/articles/Q238/9/49.ASP?LN=EN-...Quote:> If you don't want to install the client network utility, you can hack the
> registry or you could also specify the net lib in the connection string.
> Take a look at this kb article:
> > We are running a VB program (3rd party) that accesses SQL7.
> > How do we control what network protocol is used to access SQL? (ie. tcp,
> > named pipes, etc.).
> > Do we have to install and run the SQL client network utility on each PC?
> > Thanks,
1. Client Network Utility Versus Server Network Utility
When I installed SQL server Client Network Utility Tools and Server Network
Utility Tools installed. What is the different between these two?
Thanks
Sn
2. Oracle 8 and Access-Assistant
3. Client Network Utility required for Windows 95/98 clients using replication
5. SQL client : client network utility
7. using client network utility
8. Client Network Utility required for Windows 95/98 clients
9. SQL7: SQL Server Client Network Utility
10. Client Network Utility problems with SQL instance on port 1433
11. Client Network Utilities SQL 7.0
12. UNinstall SQL Server Client Network Utility