Skip to main content
Participant
October 8, 2008
Question

Framemaker 7.2 and 7.1

  • October 8, 2008
  • 6 replies
  • 1142 views
If I have a client with FM 7.1 and we have 7.2, will this present problems to him when I return the files?

Thanks,

TH
    This topic has been closed for replies.

    6 replies

    Legend
    February 11, 2009
    Mark,

    The problem may be an incompatibility between FM OLE handling and Windows SP3. You may be out of luck unless you can roll back your Windows version. OLE is unpredictable, so you might be out of luck period. The general recommendation is not to use it. For a recent, lengthy discussion on the issue, go here:

    Art Campbell, "An internal error occurred while writing imported graphics in this document. The file has been saved" #1, 16 May 2008 6:06 am

    Russ
    Participant
    February 11, 2009
    I get an error in FrameMaker 7.2 whenever I try to import a Microsoft Office Visio 2003 drawing by choosing Import > Object, then in the Insert Object dialog box, click "Create From File" button, and then browse to the file I wish to import into an anchored frame in FrameMaker.

    When I try to save the FrameMaker file, I get an error message that reads: "An internal error ocurred while writing imported graphics in this document. The file has been saved, but has lost some image data. Please report this error to Adobe Technical Support."

    I basically loose everything I've done since the last Save, and FrameMaker then creates a backup file

    OK, I'm reporting it to Adobe Technical Support. Now I'd like some solutions. Thanks.
    Participating Frequently
    February 11, 2009
    Mark

    1) This is not Adobe Technical Support. This is a user-to-user forum.
    We'd all like solutions to our problems, but you're more likely to find
    workarounds here.

    2) This thread has nothing to do with your problem. Please begin a new
    thread instead of hijacking a thread about 7.1/7.2 compatibility.

    3) Object linking and embedding (OLE) has always been somewhat broken,
    but XP Service Pack 3 really killed it. Are you on SP3? If I were you, I
    would avoid OLE entirely. Save your Visio drawings as discrete graphic
    files and import them instead.

    --
    Kenneth Benson
    Pegasus Type, Inc.
    www.pegtype.com
    February 10, 2009
    Ramji, it would be much better if you post a new thread on the forum so that people will more easily find your question.

    Also, there is a yahoo group for FM developers where you would receive more detailed information:

    http://groups.yahoo.com/group/frame_dev/

    Please be sure to specify which exact version of FM you are using.
    Participant
    February 10, 2009
    HI all...
    I am so much new to this forum and also to framemaker
    development...

    i need your help to step forward.. i am using visual Studio 2003 (vc++)
    to develop my clients.. and i would like to know the way procedure to customize our own dialog boxes.. and i found one way in the manual using .DRE templates.. i've done it and got two files with .DLG and .XDI
    extensions.. but i am unable to view it.. that i mean the tools which i added into the .DRE template in Visual Studio environment..

    I wanted to know the procedure to design our own .DRE templates and call
    that in our program while initialization or based on cases..

    Regards,
    Ramji.S
    Inspiring
    October 8, 2008
    While you may want to use MIF as a security net, I've been trading and moving files between 7.1 and 7.2 environments for several years and haven't had any problems exchanging hundreds of files.

    As I recall, all the differences in the point releases were internal bug fixes and updated import/export and graphics filters. Nothing that actually touched the data files.

    Art
    Arnis Gubins
    Inspiring
    October 8, 2008
    It shouldn't, as the file will be flagged as v.7 internally. The
    safest method is to use MIF for interchange. FM then ignores anything
    that it doesn't understand when reading from a more recent version
    (whereas with a binary FM file, the older version will refuse to open
    the more recent format).