J
Jaek
I am trying to establish an ODBC connection from Access to a remote SQL
Server database. The database resides on a company-wide network, the actual
server itself is I think in a dark room in Texas. I've mapped to the drive
where the target SQL Server database resides.
Using the ODBC applet, I come to the screen labeled 'Create a New Data
Source to SQL Server' where I can specify Name, Description, and Server. The
Server line is a dropdown that is populating itself, by what mechanism I
don't know. It is showing a list of what may be SQL Server instances on some
part of the network (a small and relatively 'local' part from what I can
see), but the target database is not there.
I tried the applet both before and after mapping a drive to the location of
the target database, and the list in the dropdown did not appear to change.
If there are suggestions on something I could do to put that target 'on the
map', that'd be great. Next question would be, is there an alternative to
using the applet?
Server database. The database resides on a company-wide network, the actual
server itself is I think in a dark room in Texas. I've mapped to the drive
where the target SQL Server database resides.
Using the ODBC applet, I come to the screen labeled 'Create a New Data
Source to SQL Server' where I can specify Name, Description, and Server. The
Server line is a dropdown that is populating itself, by what mechanism I
don't know. It is showing a list of what may be SQL Server instances on some
part of the network (a small and relatively 'local' part from what I can
see), but the target database is not there.
I tried the applet both before and after mapping a drive to the location of
the target database, and the list in the dropdown did not appear to change.
If there are suggestions on something I could do to put that target 'on the
map', that'd be great. Next question would be, is there an alternative to
using the applet?