This content has been marked as final. Show 4 replies
keeping in mind that the parameters used in test presentment may differ from the command line parameters on jfmerge, differences can certainly happen. Check in output designer under tools>options>testpresentment to see what parameters you are using. In particular, designer and jfmerge should have -aapoff and -afxon.
If you don't see anything jump at you there,send me your ifd and data file and I will be happy to have a look. By the way, unless you are using more than one mdf file, you don't need the ^form command in the data file. Just put the full path of the form file on the jfmerge command line.
Added note...if you want me to take a look at the footer problem, send me your ifd and data file.
The Output Designer Test Presentment options field has no options showing. My DAT file has -apfon -afxon -aapon on the ^job line. In addition, to get around a problem we had early on we add "ExternalSubforms=1" in the PDFPrep section of the jfmerge.ini file. We also changed the Reformat parameter in the Field section to "Trunc". We also set up the jfmerge tasks to specify a dummy form so the files in the print queue are recognizable as coming from Central but we don't want it to actually print so we have the -apg2/999 parameter on the ^job line. Early on a system tech was working on a printing problem and didn't recognize the file names and deleted them. Now, with a recognizable name, they don't get deleted.
We certainly can't use -aapoff because we have tons of forms with boilerplate only pages.
We use common tasks for many forms so I can't add the form path/name to the jfmerge command line. Besides, all of our print (except this one which is intended to solely produce a PDF) uses multiple forms even if it is just a separator/clerical instructions page and the actual form itself. We produce over 150,000 "packets" per month at 11 sites for mailing so the colored separator pages are required.
It was gone earlier today but is now back again: the top of page 2 is also showing up at the bottom of page 3 after the page 1 footer.
I'll be sending you my files, but not until after lunchtime here on the left coast.
Just a follow up to close this thread.
I sent my files to Chris and he responded with the solution, which he had alluded to in his first response to this thread. Dynamic forms
have the -aapoff option. I had initially stated I couldn't use the parameter because of all our other forms and using a common job & task. Chris pointed out that if I added it to the ^form statement that it would override any other occurances. Now, with that parameter, the actual creation of the PDF by jfmerge matches what is produced by test presentment. I just need to get with the programmer responsible for creating the DAT file and determine the best way to get the parameter added.