drive mappings

[nikki]

recently, at work, a lot of files were moved from the
s:drive to the t:drive (the s:drive & the t:drive are
network drives housed on a server for information sharing,
and were recently consolidated onto the t:drive). one of
the files moved was an access database. now, when you
open it, there are a couple of queries that will not run -
they give you an error message that says that it cannot
find the s:drive (although it and all related information
is now housed on the t:drive). other queries work
properly, and since all the information was simply copied
over to the other drive, i cannot figure out why this
particular file is having issues... any suggestions?

 

[Van T. Dinh]

* You may have linked Tables from another database which was previously
resided in S: drive. When the Queries referred to these linked Tables,
Access won't be able to find these Tables.

If this is the case, you will need to re-link these Tables and supply the
correct path to the Source database.

* In some cases, instead of the linked Tables, developers use external
Table (but not as linked Tables) in the Queries as the path to the Table /
Source database can be specified in the SQL String.

If this is the case, you will have to modify the path specified in the Query
(SQL String).

 

[Jeff Boyce]

Nikki

Consider a solution that would take into account that different PCs could
map to the underlying server using different "paths" -- don't use the "share
name" ("S:" or "T:" or "W:"!) at all! Instead, check into the use of the
UNC approach. Your path would point directly at the server, instead of at a
share name. It would look something like:

\\servername\folder\file

You'd link to this by first pointing to the network, then following/driving
down to the server name, folder, ...