This is my understanding of the process and I believe the issue is OLE
although one of the problem files we couldn't pin down an exact problem.
So I think I know what the coarse of action will be - remove all uses of
OLE. But its hard to understand why these documents seemed to work under
dzBatcher doing exactly the same steps. Its this aspect that may give me
trouble in trying to convince people to not do this.

Thanks everyone for the insights provided.

..dan


*************** 
Dan Vint 
Engineer Sr. 
BEA Systems 

Home: 510-522-4703 (generally working from home) 
Office: 408-570-8554 
IM Yahoo: dvint1_99 

dvint at bea.com 




________________________________

        From: Fred Ridder [mailto:docudoc at hotmail.com] 
        Sent: Wednesday, November 07, 2007 5:41 PM
        To: Dan Vint; framers at lists.frameusers.com
        Subject: RE: Possible Frame6+SGML Issue only MIF to Native and
OLE graphics


        Dan Vint (dvint at bea.com) asked:
        > 
        > To support OLE reading the graphic back in, do I need to have
the
        > original application? This is the primary difference I could
think of.
        > Out build machine might not have Office for something from
Word for
        > instance, but that would be common on our personal machines.

        As far as I know, OLE requires not only that the originating
application 
        be installed on every machine that will use the file, but that
it's the 
        same version of the tool and is installed in a directory of the
same 
        name in the same relation to the FrameMaker installation. It's
an 
        unreasonably tall order unless you have a *very* methodical (and
        dictatorial...) IT department, which is why it is so risky to
use OLE 
        embedding rather than simple file linking. 

        Fred Ridder



________________________________

        Peek-a-boo FREE Tricks & Treats for You! Get 'em!
<http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us>  


Notice:  This email message, together with any attachments, may contain 
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated 
entities,  that may be confidential,  proprietary,  copyrighted  and/or legally 
privileged, and is intended solely for the use of the individual or entity 
named in this message. If you are not the intended recipient, and have received 
this message in error, please immediately return this by email and then delete 
it.

Reply via email to