Re: Frame FDK gotcha

[Chris Despopoulos <cud@xxxxxxxxxx>]

Ananda Stevens wrote:
***********
When you are working with a book file, you can get the 
component ID for each chapter file in the book, but that 
ID is NOT the same as that chapter's document ID. You have
to use the component ID to get the name of the chapter file,
then open the chapter file to get its document ID. With the 
FDK's error reporting, you won't get an error message if 
you mistakenly use one ID when you should be using the 
other. 
***********

Whether or not the error reporting is sufficient, when you
think about it, it makes sense.  A book component is a child
object of a book.  A book is just a lit of filenames, with
properties attached to them (numbering, etc.), and element
stuff if the book is structured.  

A document, on the other hand, is much more.  If you try to
get document stuff out of a book component, I suspect you
get a "wrong Object Type" sort of error if you ask for it. 
And if you have internalized the FrameMaker Object Hierarchy
(you *have*, haven't you?  Hmmm???) you will instinctively
know why.

Happy programming...                            cud

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