M
MJ
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
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