-------------- Original message ---------------------- From: "Demling, Peter" <[EMAIL PROTECTED]> > Oh, you know it - I'm offering up a second pay-pal'd ice-cream to anyone who can solve this one; I'm even willing to spring for extra fudge sauce at this point - > either that or our project is really doomed this time! :) > Basically, pdf forms that are enabled for user rights, and then pre-filled via iText, lose their user rights after the first offline save in Adobe Reader: you get the dreaded "the document has changed since it was created and these rights are no longer valid" message. I just tested now with enabled_form_prefilled.pdf posted on the FAQ page at http://www.1t3xt.info/examples/browse/?page=example&id=348. I'm using Adobe Reader 8.1.2 on WinXP SP 2. Several key points observed so far surrounding this > issue: >
Peter, sorry for the previous diversion. I'll try to restrict myself this time to statements that don't prove I open my mouth to change feet. ;-) The Reader-Enabled form that Bruno used was prepared with Adobe LiveCycle Designer 8.0 (PDF 1.6), and appears to exhibit the write-once, save-once, before broken behavior you observed. I have not done any further tests to see if additional data could be entered programmatically with iText. OTOH, AcroForms that I've had Reader-Enabled by someone with Adobe Acrobat Pro 8 do not exhibit this behavior, as I am able to alternately, add data with iText, and in Reader 8.1.2, without breaking the Reader-Enabled features. In fact, one of the AcroForms has an array of "action" buttons that are fully functional, as well. IOW, no breakage observed. <snip> > So perhaps Reader is seeing the "adding of an extra processing instruction" > (namely, <?xfa generator="XFA2_4" APIVersion="2.6.7120.0"?>) that gets added > after the first save, and is taking this to mean that the document itself > (and > not simply a form field value) has changed. What do you think? > <snip> > Any suggestions are most welcome! If this ends up being an unresolveable > XFA-related issue, I'd still consider switching to a pure Acro form, but my > problem with that so far has been finding a way to convert from XFA to Acro > (we > have a 4-page static XFA form with lots of fields). Worst-case scenario if > XFA > is the problem, and we can't convert: we could re-design the whole form from > scratch using Acrobat (non-Pro) - but that would be a difficult task for our > designer. I don't have Adobe Acrobat 8 or LiveCycle Designer 8, so using anything other than AcroForms is not an option for me. That said (written), if I were in your position, I wouldn't hesitate to look into using iText itself to create the entire AcroForm. Having done this myself with a 2-page AcroForm with several hundred form fields, I can tell you the task is not as insurmountable as it may seem to be. An added benefit is that, with iText, you have absolute control over the placement of every element of the form's design that you place on each page. With a GUI form design tool, your computer screen places limitations on accuracy of placement of form elements that are simply not applicable when you generate the AcroForm with iText. I suspect this saga will continue. I hope the project bind doesn't spoil your weekend. Best regards, Bill Segraves ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Do you like iText? Buy the iText book: http://www.1t3xt.com/docs/book.php Or leave a tip: https://tipit.to/itexttipjar
