"ODBC - connection to 'SQL Server A.B.C.D' failed" error on many machines

If its SQL Server 2k then you might want to make sure that the SQL Server
driver version starts with 2000.
mine is 2000.81.9042.00
Get this by installing mdac_typ26.exe ie, ver 2.6 at least.

Check the faulty machines to see if the driver is below this.



"Ivan Starr" wrote in message
...
Hello and thank you for helping.

I have written a SQL Server database front end for a mixed
win98/winXP/win2K
Office97/2K environment. The error only happens on some machines of
varying
office software and OS. I fixed one win98/office97 machine with the
MDAC_TYP.EXE file when I saw there was no version number on the SQL Server
driver listed in the ODBC Data Sources program under the drivers tab.
However, that did not fix the same problem on other machines.

I know all the machines can ping the SQL server in qn.

What is the correct version number for the driver? Is the MDAC_TYP.EXE
file
OK to run on any machine? There are so many similar entries in the MS
'knowledgebase' about this it is very hard to know what to do.

What else needs to be in place in order to assure the ability to connect
to
an SQL Server?

What's missing here?

Thanks,

Ivan

Hello and thank you for helping.

I have written a SQL Server database front end for a mixed win98/winXP/win2K
Office97/2K environment. The error only happens on some machines of varying
office software and OS. I fixed one win98/office97 machine with the
MDAC_TYP.EXE file when I saw there was no version number on the SQL Server
driver listed in the ODBC Data Sources program under the drivers tab.
However, that did not fix the same problem on other machines.

I know all the machines can ping the SQL server in qn.

What is the correct version number for the driver? Is the MDAC_TYP.EXE file
OK to run on any machine? There are so many similar entries in the MS
'knowledgebase' about this it is very hard to know what to do.

What else needs to be in place in order to assure the ability to connect to
an SQL Server?

What's missing here?

Thanks,

Ivan