Further update on this issue. I was able to finally perform some
additional testing and here's what I found:
- Hyperlinks inserted in a regular Word document and attached to an
email do not convert to UNC.
Note the screen tip will reflect UNC but if you use Alt + F9 to
display the field codes the hyperlink will reflect the mapped drive.
(I wasn't losing my mind after all. <g>)
True, the field code will show the mapped drive, but the action taken
when the link is clicked will still go to the UNC path. There must be
some magic involved here. I wrote some VBA code to explore the
hyperlinks' properties (see below), and it confirms the behaviour I
observe: in action, hyperlinks to drive letters on network resources
resolve to UNC paths.
- Hyperlinks inserted in an email, when using Word as the email
editor, will display as a mapped link but the source reflects UNC.
The most obvious give-away is to inspect the HTML source when using Word
as the Outlook editor and composing HTML messages: it clearly shows a
link to a UNC name.
I could only come up with one workaround at this point and it isn't
the best but it does replace typing the links:
- Once the hyperlinks are inserted select them and press Ctrl + Shift
+ F9 to convert them to text.
That is just a different way to my solution which is to copy the fully
qualified file name from a file's context menu in Explorer.
As you stated above, a hyperlink's code revealed with Alt+F9 shows the
drive letter; however, I found that clicking the link will go to the UNC
path. What was going on?
I conducted this experiment:
1) Create a hyperlink to a document on our network file server (F

.
2) Copy that file to my local disk, disconnect from the network, and
create a drive letter (also F

to the directory of that file with
SUBST. For fun, I created the same directory structure under that drive
letter as I had on the file server.
3) Create a hyperlink to this document.
I now had two hyperlinks in my document, which looked exactly the same:
F:\Corporate\Finance & Accounting\CorpFinTree.xls
F:\Corporate\Finance & Accounting\CorpFinTree.xls
The first one to the network drive, the second to the SUBST'ed drive.
They were identical in appearance on screen and when field codes were
revealed with Alt+F9. However, the balloon texts were different, as was
their action: the first one wanted to go the network, the second to my
local disk. Where did that different behaviour come from?
VBA code showed why. The hyperlink properties Address and Name showed
the UNC path for the first link, but the drive letter path for the
second. So there is definitely more to hyperlinks than the field code
shows. Here's a summary of the properties for the first hyperlink:
Address: UNC
Name: UNC
Range: Drive-letter
TextToDisplay: Drive-letter
The properties for the second hyperlink are all Drive-letter.
The Word document which contains these two hyperlinks and VBA code to
show their properties is at <
http://mbednarek.com/hypertest.zip> (6,297
bytes).
The ultimate proof is of course in the eating: clicking on a hyperlink
which appears with its drive letter but where that drive letter
originally referred to a network resource will always link to that
network location by its UNC path.
I now give up. Thank you, Beth, for your assistance. I am, however,
disappointed that no one else got interested in this issue, particularly
as your own resources for testing in a network environment seem limited.