Re: Spurious invalid elements

[Kathleen James <kjames@xxxxxxxxxxxxx>]

Hi Dan,
Thanks for the tips. It seems to be more strange than that.

Three of us are working on the same book. The EDD on my PC (the master) is
dated May 19. The EDD on the other two PCs is June 2. All three files are
exactly the same except for the file date. I posted the master file to our
intranet on May 19. When the other two PCs were updated (on June 2nd) by
downloading the files from the web, they got the current date for their
EDD.

So, if I work on files and then one of the other writers opens the book
and validates elements, Framemaker "helpfully" says the file is invalid.
Even though it's not.

Moral: If you change the EDD, update all PCs at the same time.
Dear Adobe: Could we have a more meaningful error message for this sort of
event, other than  "Document contains invalid elements", please?

--
Kathleen James
Documentation Specialist
Oracle Corporation UK Ltd
Public Sector Applications
Thames Valley Park, Reading, Berkshire, UK

Dan Emory wrote:

> At 07:30 PM 6/8/00 +0100, Kathleen James wrote:
> >When we validate elements at the book level, Frame stops at various
> >chapter files and says "Document contains invalid elements". Yet when
> >you open the chapter, it says "Document is valid".
> >
> >Any thoughts, O Knowledgeable Ones?
> =========================================
> First, look at the structure view for the book file. Do any of
> the book components show up in red? If so, resolve those
> discrepancies.
>
> The most likely possibility is that some chapters within the book
> are using versions of the EDD that differ from the version of the EDD
> imported into the book file. I'd start out by importing the latest
> version of the EDD into the book file, and then, from the
> book file, importing that same EDD version into all the chapter
> files.
>
> If that doesn't solve the problem, the only other thing I
> can think of is that the book element itself in the EDD is
> specifying exclusions of elements, and there are no such
> exclusions of those same elements at the chapter level.
> This would make the chapters valid when they're checked
> individually, but not when they become part of a book
> element having such exclusions.


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **