Hi everyone
We've found workarounds (yay). Basically, it looks like the files were too
complex for FM's liking. Two things to avoid:
1. multi-page tables with conditioned rows
2. a large amount of conditional text on the first page of a file, immediately
following an imported TOC inset.
That
...@alliedtelesis.co.nz
To: framers@lists.frameusers.com framers@lists.frameusers.com
Sent: Thursday, November 10, 2011 12:49 AM
Subject: Re: Framemaker 10 crashes when changing conditional text display
setting
Hi Roman
That's interesting. I did manually save the file as MIF.
Did you try/find anything else
Hi Rebecca,
I had a similar problem 2-3 times with specific FM files. Usually, manually
saving the files as MIF and then manually saving them back as FM10 solved the
problem.
HTH,
Roman
From: rebecca officer rebecca.offi...@alliedtelesis.co.nz
To:
Hi Winfried
I'm embarrassed to admit I hadn't thought of that! But it didn't work.
I opened a blank file, imported all settings from our template, and pasted in
the contents of a sick file. It still crashed. I even went back to an old
template from before we started using build expressions,
Hi Roman
That's interesting. I did manually save the file as MIF.
Did you try/find anything else? Anything that your sick files had in common?
We're speculating it's FM's pagination engine getting upset with CT causing
repeated major changes to pagination. But that's pure speculation!
