Cindy M. wrote:
Hi ,
I understand that IncludeText relies on absolute paths. More
specifically, the behavior of how Word looks for files that are listed
in the IncludeText field is too brittle to be reliable. Putting all my
"included" files into one bucket (read: directory) isn't a viable
solution for me.
No, IncludeText supports both absolute as well as relative paths. But if
you don't all the files in "one bucket" you'd prefer absolute paths,
wouldn't you?
Cindy,
I'd like to keep a "working" IncludeText directory tree on my
workstation and a "production" IncludeText directory on the network
server. I'd make updates and changes to the working directory and then
copy them to the network server. Once a document is ready for
production and I move it to the network server, the link to the
original working IncludeText file will be broken by using an absolute
path to my local workstation. I'd prefer to keep the linked material on
the network server.
I experimented with using a relative path in an IncludeText field but
Word complained: "Error! Not a valid file name." Here's the path:
"\\Production\\Users Manuals\\WORD DOC VERSION\\The Document.doc"
Any thoughts?
Thanks,
Jeff