Scott,
the crash is sure under certain conditions.

What I can see is that showing certain pattern of "conditionals" the crash always happens, while the same book with other show/hide combination of conditionals it doesn't.

The exact moment where the FrameMaker crashes and gives the error is during the F_ApiSave call inside this piece of code:

BOOL DMFrameMaker::SavePDF(CString sPDFLocation)
{
F_PropValsT params, *returnp;

params = F_ApiGetSaveDefaultParams();
returnp = NULL;

int i = F_ApiGetPropIndex(&params, FS_FileType);
params.val[i].propVal.u.ival = FV_SaveFmtPdf;

m_foDocId = F_ApiSave(m_foDocId,
(unsigned char *) sPDFLocation.GetBuffer(512),
&params,
&returnp);

F_ApiPrintSaveStatus(returnp);

return TRUE;
**

I tried to set the conditionals manually but the same conditionals aren't giving problems to the FrameMaker in an interactive run.
So I fear it can be a problem inside my program or the API, but I don't know how to inspect further (keep in mind that with a single different conditional to show/hide it works well).

Please, help me discover something more about this mess!
Thanks,
n3u.