Help! Can't connect via ODBC DSN file to SQL server 2005 i..

I am using SQL Server 2005 and using a database program that was installed
on the C:\ drive of the server. The 12gb partition has 1.8gb left and I
need to move it to the 550gb D:\ drive. Simple, yes and no. I have an
external MS Access 2003 report program that connects to the database via a
ODBC DSN file connection that I used to link certain tables.

The question is what happens to my connection if I move the SQL database to
the other drive? Will I lose my connection?

I shouldn't, so I thought. So I wanted to test my theory. The program I am
connecting to allows you to install a training or release version of the
database on the server, which I created a TEST file installed to the D:\
drive where I want the real one. I have also played with Access in creating
a new project file and an upsized MDB program on the same server. By
default they were created on the C:\ drive and I have access to them.

Now I tried to create a new ODBC connection to my TEST database that I
installed on D:\. I get to the part where you select which database to
connect to and it is not listed as one of the default files on the server.
In fact only the ones found on the C:\ drive are listed except the sample
databases like Northwind. There is no way to type in the name I want
because it says it doesn't exist. If I copy the database file that is
listed, that copy is not listed either.

Another question: how do you make a database file part of the default
listing so it can be connected too? Or do I just have to figure out how to
use connect strings in VBA? Is there a way to edit this in the server
manager library of programs?

Bob

SQL Server is not a file based database system. You don't
connect to physical files, you connect to a SQL Server
instance. When I connect to a SQL Server instances, I don't
need any knowledge of the physical files, their locations,
etc. Files and locations don't matter to me as a client
connecting to SQL Server. If the files on SQL Server are
moved one day, it makes no difference to me as a client
connecting to SQL Server. Those things are transparent to me
connecting to SQL Server. I connect to an instance so the
location of the files doesn't matter. It only matters
internally to SQL Server.
Databases that are available to a user on SQL Server will
show up in the drop down when creating DSNs. Again, the
files themselves makes no difference.
I can't tell from your post if you created a test database
or a test instance - creating a test file doesn't mean much.
If you created another instance, you need to connect using
ServerName\InstanceName. To connect, You would need to make
sure the browser service is running as well

-Sue

On Sun, 8 Apr 2007 17:45:59 -0500, "Bob"
wrote:

>I am using SQL Server 2005 and using a database program that was installed
>on the C:\ drive of the server. The 12gb partition has 1.8gb left and I
>need to move it to the 550gb D:\ drive. Simple, yes and no. I have an
>external MS Access 2003 report program that connects to the database via a
>ODBC DSN file connection that I used to link certain tables.
>
>The question is what happens to my connection if I move the SQL database to
>the other drive? Will I lose my connection?
>
>I shouldn't, so I thought. So I wanted to test my theory. The program I am
>connecting to allows you to install a training or release version of the
>database on the server, which I created a TEST file installed to the D:\
>drive where I want the real one. I have also played with Access in creating
>a new project file and an upsized MDB program on the same server. By
>default they were created on the C:\ drive and I have access to them.
>
>Now I tried to create a new ODBC connection to my TEST database that I
>installed on D:\. I get to the part where you select which database to
>connect to and it is not listed as one of the default files on the server.
>In fact only the ones found on the C:\ drive are listed except the sample
>databases like Northwind. There is no way to type in the name I want
>because it says it doesn't exist. If I copy the database file that is
>listed, that copy is not listed either.
>
>Another question: how do you make a database file part of the default
>listing so it can be connected too? Or do I just have to figure out how to
>use connect strings in VBA? Is there a way to edit this in the server
>manager library of programs?
>
>Bob
>