Hi!

I already did that test, selecting manually the exact conditionals patten that causes the FrameMaker crash. It works and creates a PDF without problems.

Keeping in mind that there's the chance that, cause I don't know how to use the FrameMaker directly, I'm not reproducing a sequence of actions that equals what my application does, the result of the test tends to make me think that:
- the document is good in itself;
- considering that my application works well with other conditionals patterns and that works also well if I produce a MIF instead of a PDF with the same pattern, I tend to believe that my application is always doing the same (good) work;
- there's only one actor left that has to be considered: the FDK API layer.

I'm open to your considerations about my logic.

Thanks alot for your attention,
n3u.