|
Home > Archive > MS SQL Server Connectivity > April 2005 > Re: what does the SQL Server Client Tools (Client Connectivity Onl
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: what does the SQL Server Client Tools (Client Connectivity Onl
|
|
| Cathy Boehm 2005-04-01, 8:01 pm |
| Yes,
Tell me me about it.
I have an application that I am suspecting uses DB-LIB to talk to the SQL
Server and I would always have to do the install of Client Network Utility on
each workstation to go along with the app. But lately I had a user that could
do without it - Go figure?
And then I ran into the user who was missing the Network DB Library
Communications Layer when I installed Client Network Utility 2000 on his
machine to talk to SQL Server 2000 Server, so I had to revert to the SQL
Server Client Network Utility 7.0 to make it work.
"Vikram Vamshi" wrote:
> My understanding was that MDAC included the client network libraries ...
>
> MDAC is a prime example of DLL hell problem, it comes in many versions and
> is bundled with many microsoft products.
>
> As long as the client machines have MDAC2.6 (or higher) you will be able to
> connect to sql server.2000
> The following versions of windows come bundled with MDAC
> WinXP
> Win2K
>
> Lower versions of MDAC might also work as long as you are not using a named
> instance of SQL Server.
>
> A quick way to find your version of MDAC is to look up the following
> registry entry, it is not reliable but works in most cases:
> HKEY_LOCAL_MACHINE\S
OFTWARE\Microsoft\Da
taAccess\Version
>
> hth
> --
> Vikram Vamshi
> Eclipsys Corporation
> "Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
> news:sm6l41l30f6qq0i
dp4lb5ascf0vkb5amas@
4ax.com...
>
>
>
| |
| Sue Hoegemeier 2005-04-03, 8:01 pm |
| That is correct. MDAC does not include ntwdblib. You need to
install the client connectivity components (or use
sqlredis). Other applications may distribute ntwdblib which
is why one of the users may have not experienced the error.
Per the Redist.txt file on the SQL Server CD, you can
redistribute ntwdblib.
You can find the files installed by MDAC in the MDAC
manifest. I believe Vines and Apple Talk as well as the Jet
drivers are the other pieces you won't get with just MDAC.
http://support.microsoft.com/?kbid=828396
-Sue
On Fri, 1 Apr 2005 14:33:01 -0800, "Cathy Boehm"
< CathyBoehm@discussio
ns.microsoft.com> wrote:
[color=darkred]
>Yes,
>Tell me me about it.
>I have an application that I am suspecting uses DB-LIB to talk to the SQL
>Server and I would always have to do the install of Client Network Utility on
>each workstation to go along with the app. But lately I had a user that could
>do without it - Go figure?
>And then I ran into the user who was missing the Network DB Library
>Communications Layer when I installed Client Network Utility 2000 on his
>machine to talk to SQL Server 2000 Server, so I had to revert to the SQL
>Server Client Network Utility 7.0 to make it work.
>
>
>"Vikram Vamshi" wrote:
>
|
|
|
|
|