Dave,
Your assumption that catalog path order is important is correct. The
catalog uses that old inventory approach of FIFO (first in, first out). If
you have two public identifiers pointing to different documents, the first
one encountered will be the one that is resolved. So not only is the
catalog path sequence important, but so is the order of entry in the
catalog file itself.
One other thing to keep in mind with Epic on Windoze. When working from a
command line or script input, Epic does not like the space in the
C:\program files\epic
path unless it is either delimited by single or double quotes, or you use
the tilde "~" to shorten the path name. Even in the APTPATH variable.
I am adding this as you said when you made the changed the order to match
the other workers path things worked. I would believe you have a duplicate
catalog entry or the path is resolved prior to getting to the space. Did
your error message say something like "file not" something like a valid
command?
Lynn E. Hales
Information Technology Consultant
lhales@csc.com
(757) 262-3495
Dave Burkhart
<burkhard to:=" adepters@arbortext.com=" <br="/> @spar.ca> cc:
Sent by: Subject: Re: RE: RE: Hi Adepters,
owner-adepter
s
05/08/2002
10:31 AM
Please
respond to
adepters
The only entry in my Options/Preferences/File/Graphics Path box was to the
catalog I changed.
Turns out the problem is path related though. I had another person open the
document on her machine and the graphic resolved correctly.
These were her Options/Preferences/File/Catalog Path entries:
k:\epicdoctypes\dnd\cals\source\doctypes;
K:\data\cftos\000mn001book3;
k:\data\gen_pub\000mn001book3;
C:\Program Files\Epic\doctypes;
k:\epicdoctypes\dnd\cals\source\entites\fosi\fragment
These were mine:
k:\epicdoctypes\dnd\cals\source\doctypes;
K:\dnd\cals\source;
C:\Program Files\Epic\doctypes;
k:\data\gen_pub\000mn001book3;
k:\data\cftos\000mn001book3;
k:\epicdoctypes\dnd\cals\source\entites\fosi\fragment
The catalog I had changed was in k:\data\cftos\000mn001book3 which appeared
in both Catalog Path boxes.
When I made my paths identical to my co-worker's, the graphic resolved on
my machine.
So it looks like the order in which the paths appear is important.
Thanks for your help folks.
Dave
>>> "Benton, Ed L" <-> 05/08 7:24 AM >>>
Good point, Lynn. There are also those damn "epicprefs.acl" files that can
have graphics paths in them that will override anything set in an APTGRPATH
environmental variable or pubrc or doctype.acl file. Anything that gets
changed or entered into that Options/Preferences dialog graphic path field,
and then saved, will get written to the "epicprefs.acl" file.
