[skc[_2_]]

Macros in Excel2000 reference directories on the network
through mapped drives, hence the map is listed in the
Macro: e.g. F:\client\new\directory

We are now mg servers and it is proving a problem to go
through the VB script and amend the mapped letter to point
to a new location (I know I can do a find/replace!!)

Is there any easier method of deploying paths in Macros,
so if we go through another server change, we do not face
any agro?

thanks,

skc

[Patrick Molloy[_3_]]

if the file structure on the server is the same then if
you map the server to the same drive, it won't affect
your code at all.

Patrick Molloy
Microsoft Excel MVP

-----Original Message-----
Macros in Excel2000 reference directories on the network
through mapped drives, hence the map is listed in the
Macro: e.g. F:\client\new\directory

We are now mg servers and it is proving a problem to go
through the VB script and amend the mapped letter to
point
to a new location (I know I can do a find/replace!!)

Is there any easier method of deploying paths in Macros,
so if we go through another server change, we do not
face
any agro?

thanks,

skc
.

[Bob Phillips[_5_]]

On the latter point of an easier method, it is a good practice to setup
constant for frequently used, or variable, values. In this way, you could
have a constant for these paths, all in one easily accessible, easily
changed place.

I put my constants in an independent module, with shared code.

--
HTH

-------

Bob Phillips
... looking out across Poole Harbour to the Purbecks


"skc" wrote in message
...
Macros in Excel2000 reference directories on the network
through mapped drives, hence the map is listed in the
Macro: e.g. F:\client\new\directory

We are now mg servers and it is proving a problem to go
through the VB script and amend the mapped letter to point
to a new location (I know I can do a find/replace!!)

Is there any easier method of deploying paths in Macros,
so if we go through another server change, we do not face
any agro?

thanks,

skc

[Tom Ogilvy]

Just to echo what Patrick said - it seems to me that with a little
discipline, using the drive name would be more permanent than trying some
alternative like the Server name, if changing servers is the point of
concern. If you will be changing file locations, so that either or all of
Server Name and Drive letter and directory could change, then you might have
common file (or registry entries) that scripts reference to set a variable
value and use the variable in your code.

Regards,
Tom Ogilvy


"Patrick Molloy" wrote in message
...
if the file structure on the server is the same then if
you map the server to the same drive, it won't affect
your code at all.

Patrick Molloy
Microsoft Excel MVP

-----Original Message-----
Macros in Excel2000 reference directories on the network
through mapped drives, hence the map is listed in the
Macro: e.g. F:\client\new\directory
er
We are now mg servers and it is proving a problem to go
through the VB script and amend the mapped letter to
point
to a new location (I know I can do a find/replace!!)

Is there any easier method of deploying paths in Macros,
so if we go through another server change, we do not
face
any agro?

thanks,

skc
.