ADO MSSQL 2000

I am using ADO with D5 enterprise. With all updates applied.
I have no problems running the program but when the users try to run it they get the following error message 'Specified SQL Server not found'. I am using the OLE DB Provider for SQL Server, Windows NT integrated Security, I have the correct database selected with the users given rights to that database.

All of us are running Windows 2000 Prof. with all updates applied. I thought MDAC was installed with Win2k. Is it? I don't remember installing it on my machine.

Ross
LVL 1
bozo7Asked:
Who is Participating?
 
StefaanConnect With a Mentor Commented:
Hi,

Well just to make sure, did you install the Client Connection utilities on the PC's ? I remember I had a similar problem and after installing the Client Toools it worked.

Best regards,


Stefaan
0
 
EpsylonCommented:
Difficult to say:
- Firewall is blocking the connection (unlikely)
- Servername is unknown to clients
- Security misconfiguration

Can the clients connect using a specified username and password?
0
 
EpsylonCommented:
Btw, you posted this question twice...
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

 
bozo7Author Commented:
I will try that.
0
 
bozo7Author Commented:
Nope I specified the username and password and the same error.
Ross
0
 
EpsylonCommented:
Can the clients 'ping' to the server?
0
 
bozo7Author Commented:
Yes, They can Terminal Server to it and browse the network to find it. So they can see the server on the network.
Is there a way to define the connection string at runtime? I noticed that the connection string has my computer name it. I assume that ADO changes that at runtime but just in case.
Does it matter if they are running the exe off a network drive?

Ross
0
 
bozo7Author Commented:
I figured out why that error message occurs. We are using TCP/IP on our SQL server not named pipes. ODBC by default is using Named Pipes. I went into the ODBC manager and created a connection, told it to use TCP/IP, deleted that connection, and now my program works.
So is there a way to tell ado to use tcpip not named pipes?
0
 
EpsylonCommented:
ODBC??? Why using ODBC? You don't need it at all.
0
 
bozo7Author Commented:
I am not using ODBC but I went into the ODBC Connection Manager and told it to use TCP/IP not named pipes and then my ADO connection worked. I don't know why but it does. Now I trying to figure out how to use TCP/IP not named pipes with ADO by default.
0
 
EpsylonCommented:
That's weird...
0
 
bozo7Author Commented:
That is the other thing I was wondering. I know that ADO allows you to connect to MSSQL without the client connection tools, but does it work better if we install them? Do we need to install both MDAC (for none Win2k clients) and the client connection tools?

Probably is best to do that is suppose.

Ross
0
 
bozo7Author Commented:
Not what I was hoping for but it works. It also works if you just install the MDAC components. I think I will go that route rather than install SQL Server libs on all the computers.

Ross
0
 
StefaanCommented:
Hi,

Well, indeed installing the MDAC components on the Client PC's should do the trick too.

Best regards,


Stefaan
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.