Skip navigation
Currently Being Moderated

Question on conditional text design

Sep 27, 2012 1:50 PM

Posted in the wrong forum, re-posting here.

I have a relatively large book (230 pages) with dozens of tables and 100's of graphics. I need 4 versions of this book. One for each grade level (3) and one if content for all 3 grades is sold as a "master course."  Other than implementing the conditional text, the book is ready to go. I have tried a couple different ways to approach the  tables conditionally (some of which are in Text Frames, some just anchored to a page ) but I don't get very far.  Applying the Conditional Text tags ( with different colors and markers for each)seems to make it crash (i.e. almost duplicatable unlike the "normal" 3-4 crashes I experience on a daily basis the last month that are just random). Sidenote: I was very happy to see that they are going to fix the book printing crash...


Cross reference markers are involved in these conditional sections, and I have my suspicions that they are a root culprit of my other crash problems, but then FM crashed when applying conditional text to a section that *didn't* have a x-ref, so I don't know what to think.


I need to get this out by Monday. So my question is this, if I need 4 tables in a page (one for each version) am I better off just making 4 copies of the book and compiling that way? I sold the client on FM mostly because of the ability to compile multiple docs from one base I really hate to have 4 copies when I give her the source. I know you can highlight individual rows in a table for a version (so I could make one really big table for 3 of the versions and just choose different rows), but this is a thing that seems almost certain to make it crash as well.  And the master tables have an additional column as well as a row so I would still need 2 tables per doc if I could get the conditionals to quit crashing. Is there some better way to "design" this that an experienced FMer could suggest? Some custom utility that works even if it isn't free?


Just in case someone asks this:


System Config

FM 11

new install in August, not upgraded

Files are all new and native to FM11

Windows 7-64 bit

20 gig of memory

2 TB drive - local C:/


Thanks for any suggestions on this.

  • Currently Being Moderated
    Sep 27, 2012 2:07 PM   in reply to panangle

    What you are trying to do is completely stable in FM7. We do it, as long as we avoid things like overlapping conditions (which are theoretically possible to emulate in FM9 & later using Conditional Expressions).


    Conditional table row is also stable in FM7.


    My guess is that FM11 conditions are not stable.


    You could do 4 versions of each table, and just conditionalize the anchor as a workaround.

    Mark as:
  • Currently Being Moderated
    Sep 27, 2012 2:25 PM   in reply to Error7103

    I concur with Error on this - make 4 versions of each table, conditionalizing the anchor. This is to avoid anything "messy" that FM probably won't be able to handle (causing a crash).


    For some reason, FM10 and FM11 seem to just hate conditional tags. I have a much smaller document, and FM10 crashes on me when showing/hiding conditions at the book level; however, I am able to change the show/hide settings at the "chapter" (files within the book) level - go figure.


    I'm sure this isn't the answer you want to hear, but I think it's the safest bet and will you save you the headache and time in the long run...



    Mark as:
  • Currently Being Moderated
    Sep 27, 2012 3:45 PM   in reply to panangle

    It appears that you forgot to conditionalize the table anchor itself. Put your cursor by the paragraph marker and hit the Home key (I usually hit it a bunch of times to make sure). Then, hold down Shift and use the right arrow key until the entire table is highlighted. Then apply your tag.


    Good luck!



    Mark as:
  • Currently Being Moderated
    Sep 28, 2012 12:31 AM   in reply to smittywriter412



    I do not agree.

    With my files and on my system FrameMaker 8 crashed much more

    often when I worked on conditions than FrameMaker 10. (However,

    also FrameMaker 8 didn’t crash “often”. Once every 2 to 4 weeks.)

    A MIF wash always helped.


    Best regards



    Mark as:
  • Currently Being Moderated
    Feb 25, 2014 8:30 AM   in reply to panangle

    Can you post the menu path? I copied over the dll and don't see a "Book Utilities" menu after restarting FrameMaker.

    Mark as:
  • Currently Being Moderated
    Feb 25, 2014 9:16 AM   in reply to IZM

    You also have to add the following line to the [APIClients] section of your maker.ini file:




    MIFwash=Standard, MIF Wash, fminit\BookComponentMIFWash.dll, all





    The menu will only appear when you have a Book file open and selected (i.e. in focus) in FM.


    [Links corrected by moderator]

    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points