1. how to suppress auto-conversion of absolute path in hypertext link in
word
documents?
2. how to deal with link target with space in the filename or directory
path?

I am talking about plain word 2003 document not html. The conversion leaves
hypertext links
to other documents in the same server likely unusable ( 100% failure for
target files with space in the name or path).

it appears that word documents including the ones form ofc 2003 tend to
convert absolute path to relative. consequently if a document is produced
in a domain pc and stored in the pc will have its target link to the server
always
work.

However when the same document is then saved to server, the links got
converted to relative ..\..\... to the stored location..

e.g. if X: is mapped to \\aSvr\Xshare and a document hypertext link (
produced
with Ctl-K) link of x:\someDirPath\y.doc works as long the document is
stored other than on the server. when the same document is saved, let's say
y:\DriPathb\whatever.doc where y is another mapped drive pointing to aSvr,
The same hypertext link got converted into relative link. That then will
not work;control click on the link will not go anywhere

When you create your hyperlinks, set the address explicitly to what you want
(relative or absolute) on the Hyperlinks dialog. Word won't change it.


"gs" wrote in message
...
1. how to suppress auto-conversion of absolute path in hypertext link in
word
documents?
2. how to deal with link target with space in the filename or directory
path?

I am talking about plain word 2003 document not html. The conversion
leaves hypertext links
to other documents in the same server likely unusable ( 100% failure for
target files with space in the name or path).

it appears that word documents including the ones form ofc 2003 tend to
convert absolute path to relative. consequently if a document is produced
in a domain pc and stored in the pc will have its target link to the
server always
work.

However when the same document is then saved to server, the links got
converted to relative ..\..\... to the stored location..

e.g. if X: is mapped to \\aSvr\Xshare and a document hypertext link (
produced
with Ctl-K) link of x:\someDirPath\y.doc works as long the document is
stored other than on the server. when the same document is saved, let's
say
y:\DriPathb\whatever.doc where y is another mapped drive pointing to aSvr,
The same hypertext link got converted into relative link. That then will
not work;control click on the link will not go anywhere

but that is true only if the document is store on a pc not in a server with
link to other shares or drives on the same server! At least with the DC
file server running on W2k3.

Or are you saying you had produced a document as I described in my first
thread and it worked?

Have you tried with target files that have space in the file name or path?
That works too if one stores the document on a domain PC instead of DC

"Jezebel" wrote in message
...
When you create your hyperlinks, set the address explicitly to what you
want (relative or absolute) on the Hyperlinks dialog. Word won't change
it.


"gs" wrote in message
...
1. how to suppress auto-conversion of absolute path in hypertext link in
word
documents?
2. how to deal with link target with space in the filename or directory
path?

I am talking about plain word 2003 document not html. The conversion
leaves hypertext links
to other documents in the same server likely unusable ( 100% failure for
target files with space in the name or path).

it appears that word documents including the ones form ofc 2003 tend to
convert absolute path to relative. consequently if a document is
produced
in a domain pc and stored in the pc will have its target link to the
server always
work.

However when the same document is then saved to server, the links got
converted to relative ..\..\... to the stored location..

e.g. if X: is mapped to \\aSvr\Xshare and a document hypertext link (
produced
with Ctl-K) link of x:\someDirPath\y.doc works as long the document is
stored other than on the server. when the same document is saved, let's
say
y:\DriPathb\whatever.doc where y is another mapped drive pointing to
aSvr,
The same hypertext link got converted into relative link. That then
will
not work;control click on the link will not go anywhere

It's got nothing to do with where the document is stored. Word is confusing
in that when it displays the screentip for a link, it displays the 'local'
path to the target; but this is only for display purposes. To avoid the
confusion, enter your own screentips, then the whole thing is invariant.





"gs" wrote in message
...
but that is true only if the document is store on a pc not in a server
with link to other shares or drives on the same server! At least with the
DC file server running on W2k3.

Or are you saying you had produced a document as I described in my first
thread and it worked?

Have you tried with target files that have space in the file name or path?
That works too if one stores the document on a domain PC instead of DC

"Jezebel" wrote in message
...
When you create your hyperlinks, set the address explicitly to what you
want (relative or absolute) on the Hyperlinks dialog. Word won't change
it.


"gs" wrote in message
...
1. how to suppress auto-conversion of absolute path in hypertext link in
word
documents?
2. how to deal with link target with space in the filename or directory
path?

I am talking about plain word 2003 document not html. The conversion
leaves hypertext links
to other documents in the same server likely unusable ( 100% failure for
target files with space in the name or path).

it appears that word documents including the ones form ofc 2003 tend to
convert absolute path to relative. consequently if a document is
produced
in a domain pc and stored in the pc will have its target link to the
server always
work.

However when the same document is then saved to server, the links got
converted to relative ..\..\... to the stored location..

e.g. if X: is mapped to \\aSvr\Xshare and a document hypertext link (
produced
with Ctl-K) link of x:\someDirPath\y.doc works as long the document is
stored other than on the server. when the same document is saved, let's
say
y:\DriPathb\whatever.doc where y is another mapped drive pointing to
aSvr,
The same hypertext link got converted into relative link. That then
will
not work;control click on the link will not go anywhere

I wish what you said is true.

I actually tried creating a doc with target link to domain controller and
stored locally on the domain PC. the links works from there even after
re-opening, and editing, saving.

The moment that same document is saved on the DC shared volume. the target
link got changed to relative link and would not work. Even if I add base
still would not work. I did not rely to the screentips,
I actually highlighted the link and press control K to view the target link

BTW, it does not matter whether I used in the target link UNC or drive
mapped convention


"Jezebel" wrote in message
...
It's got nothing to do with where the document is stored. Word is
confusing in that when it displays the screentip for a link, it displays
the 'local' path to the target; but this is only for display purposes. To
avoid the confusion, enter your own screentips, then the whole thing is
invariant.





"gs" wrote in message
...
but that is true only if the document is store on a pc not in a server
with link to other shares or drives on the same server! At least with
the DC file server running on W2k3.

Or are you saying you had produced a document as I described in my first
thread and it worked?

Have you tried with target files that have space in the file name or
path? That works too if one stores the document on a domain PC instead of
DC

"Jezebel" wrote in message
...
When you create your hyperlinks, set the address explicitly to what you
want (relative or absolute) on the Hyperlinks dialog. Word won't change
it.


"gs" wrote in message
...
1. how to suppress auto-conversion of absolute path in hypertext link
in word
documents?
2. how to deal with link target with space in the filename or directory
path?

I am talking about plain word 2003 document not html. The conversion
leaves hypertext links
to other documents in the same server likely unusable ( 100% failure
for target files with space in the name or path).

it appears that word documents including the ones form ofc 2003 tend to
convert absolute path to relative. consequently if a document is
produced
in a domain pc and stored in the pc will have its target link to the
server always
work.

However when the same document is then saved to server, the links got
converted to relative ..\..\... to the stored location..

e.g. if X: is mapped to \\aSvr\Xshare and a document hypertext link (
produced
with Ctl-K) link of x:\someDirPath\y.doc works as long the document is
stored other than on the server. when the same document is saved,
let's say
y:\DriPathb\whatever.doc where y is another mapped drive pointing to
aSvr,
The same hypertext link got converted into relative link. That then
will
not work;control click on the link will not go anywhere

1. In a non-html document, Word always stores hyperlinks as relative. The
only thing you have control over is what they are relative to, this by
setting a hyperlink base under File Properties (Summary tab). You can get
some strange effects when you change the base but if you update all fields
(Ctrl+A, F9) it should be correct.

2. All spaces need to entered as %20. This should happen automatically if
you use the hyperlinks dialog.

--
Enjoy,
Tony

"gs" wrote in message
...
1. how to suppress auto-conversion of absolute path in hypertext link in
word
documents?
2. how to deal with link target with space in the filename or directory
path?

I am talking about plain word 2003 document not html. The conversion
leaves
hypertext links
to other documents in the same server likely unusable ( 100% failure for
target files with space in the name or path).

it appears that word documents including the ones form ofc 2003 tend to
convert absolute path to relative. consequently if a document is produced
in a domain pc and stored in the pc will have its target link to the
server
always
work.

However when the same document is then saved to server, the links got
converted to relative ..\..\... to the stored location..

e.g. if X: is mapped to \\aSvr\Xshare and a document hypertext link (
produced
with Ctl-K) link of x:\someDirPath\y.doc works as long the document is
stored other than on the server. when the same document is saved, let's
say
y:\DriPathb\whatever.doc where y is another mapped drive pointing to aSvr,
The same hypertext link got converted into relative link. That then will
not work;control click on the link will not go anywhere

Did you try making the following setting change?
In Word go to Tools, Options, and select the "General" tab.
At the bottom of the menu, there is a button that says "Web Options". Click
that and go to the "Files" tab.
There is a setting that says "Update links on save" - uncheck it, and then
select OK to save the change.

Update your hyperlink and see if the path changes.


"gs" wrote:

1. how to suppress auto-conversion of absolute path in hypertext link in
word
documents?
2. how to deal with link target with space in the filename or directory
path?

I am talking about plain word 2003 document not html. The conversion leaves
hypertext links
to other documents in the same server likely unusable ( 100% failure for
target files with space in the name or path).

it appears that word documents including the ones form ofc 2003 tend to
convert absolute path to relative. consequently if a document is produced
in a domain pc and stored in the pc will have its target link to the server
always
work.

However when the same document is then saved to server, the links got
converted to relative ..\..\... to the stored location..

e.g. if X: is mapped to \\aSvr\Xshare and a document hypertext link (
produced
with Ctl-K) link of x:\someDirPath\y.doc works as long the document is
stored other than on the server. when the same document is saved, let's say
y:\DriPathb\whatever.doc where y is another mapped drive pointing to aSvr,
The same hypertext link got converted into relative link. That then will
not work;control click on the link will not go anywhere