A workbook whose full path on a Novell fileserver is

\\LC30\VOL10\USERS\NICK\ResearchandDevelopement\Wh olesaleRevenue\application.xls

contains a VBA library reference to

\\LC30\VOL10\USERS\NICK\ResearchandDevelopement\li brary.xls



When I copy application.xls to a folder (shared by other users) called

\\LC10\VOL10\POOL\SHARED\ResearchandDevelopement\W holesaleRevenue\application.xls

and open it, the original library in

\\LC30\VOL10\USERS\NICK\ResearchandDevelopement\li brary.xls

is picked up. This seems logical enough: The reference information
stores the full path of the library.


However, if another user with access to the shared folder but NOT to
my personal folder \\LC30\VOL10\USERS\NICK\ResearchandDevelopement\
opens the exact same copy of application.xls they end up with the
following copy of library.xls opened by the reference in
application.xls:

\\LC10\VOL10\POOL\SHARED\ResearchandDevelopement\l ibrary.xls

This would imply that the reference information on the library
includes a relative path to the the location of application.xls, if
the original full path is not accessible.

Does anyone know what the rules are for determining which copy of a
library reference VBA chooses?

Thanks for you insights.

NIck