Groups | Blog | Home
all groups > sql server odbc > october 2003 >

sql server odbc : ODBC DSN Setup not seeing SQL2K db in dropdown


stevenyberg NO[at]SPAM hotmail.com
10/14/2003 11:13:27 AM
When I attempt to create an ODBC DSN (User or System) using the SQL
Server driver and NT authentication, most databases are not visible in
the dropdown. The database I need to link to, named "DEV_CORP", is
setup as my NT accounts default. So I can create the DSN and it works
fine if I leave that db entry blank. But I want to specify the db name
in the DSN instead, because I eventually will have TEST_CORP, DEV_FIN,
or other db's on the same server. So overall, the problem is that
DEV_CORP is not visible in the db dropdown.

When I use Access 2000 ADP (Access Data Projects) - which uses OLEDB
instead of ODBC - I can see and link to all of the databases (those I
have rights to obviously) - the dropdown is full of all the databases
(most are named like DEV_*).

Is this caused by my fairly old ODBC/MDAC? Its a corporate PC and they
frown on individual upgrades, but if an updated MDAC would fix this, I
can get the ok to do it.

SQL Server ODBC Driver 2000.80.380 (4/11/2001) - I assume from MDAC
2.6 SP1.
Windows 2000 Pro sp2, Office 2000 sr1

Any ideas would be great, thanks,

rboyd NO[at]SPAM onlinemicrosoft.com
10/16/2003 8:18:32 PM
It is possible that it is an MDAC issue. If it is, the problem is most
likely in the SQL Server ODBC driver (sqlsrv32.dll). As a simple test to
see if this is the problem, see if you can locate a copy of the
sqlsrv32.dll from MDAC 2.5 (version 3.70.0820). Rename the file on the
client machine and replace it with the older one. Check the DSN. If you can
see the databses then it could be an MDAC problem. You might be able to
resolve it by just re-installing the version of of MDAC currently on the
machine.

Rand
This posting is provided "as is" with no warranties and confers no rights.
AddThis Social Bookmark Button