Linked Table Manager Question

[Guest]

I recently inherited responsibility for a number of A2K3 databases within my
organization, but the original developers are no longer around to consult
with and documentation is very lacking...

Most of our databases reside on servers on our network with some resident on
PCs but the problem is with how A2K3's linked table manager identifies the
location of the target tables (etc.).

+ Currently it identifies the locations by their mapped drive location
(e.g.: O:\share\db1 directory ...).

+ My preference would be to identify the location by the exact server name
and directory location
(e.g.: \\my server\theshare$\share\db1 directory ...)

With the first option, using mappings is that if any user's mappings do not
match the developer's mapping we have a problem.

Is it possible to have the Link Manager use the server addresses rather than
local drive mappings and retain it? If so, please tall me how I can do this.

Thanks in advance for your assistance.

Mike

 

[Rob Parker]

I'm not sure if there's a way to force the Linked Table Manager (LTM) to use
UNC names directly. However, if you open the LTM and check the "Always
prompt for new location" box, then select the linked tables with mapped
drive names, you can then enter the full UNC name in the browse dialog box
for each table. This is probably fine for a once-off, to convert all
existing links.

Another alternative would be to use some code to refresh the links (eg. the
routine on The Access Web site, at
http://www.mvps.org/access/tables/tbl0009.htm), and in that code include a
call to a function to convert from mapped drives to UNC paths; code to do
that is available on the same site, at
http://www.mvps.org/access/api/api0003.htm

HTH,

Rob