I have a PDF file with fields to fill in.
On my machine with “Acrobat Reader DC” (2015 Release | Version 2015.016.20045), I can fill in the fields, save the file & email the file (from within Reader), and the data remains in the fields.
We have another user in the office running “Acrobat Reader X” (Version 10.1.1) who can fill in the fields, but cannot save the file (File|Save As). She can email the file from within Reader, but a blank copy of the document is sent, not a copy with the filled in data.
When she opens the document she gets this message:
And this message when she attempts to clicks on a field or save the document with data in the fields:
When I click the "Standards" icon in my version (Reader DC), it tells me:
- Conformance
- Standard: PDF/X-4
- ISO Name: ISO 15930-7
- OutputIntent
- Identifier: CGATS TR 001
- Info U.S. Web Coated (SWOP) v2
None of this means a thing to me, but I thought it might be useful to someone who knows more.
When I select Document Properties it reports (selected, relevant looking fields only):
- Description tab
- Application: Adobe InDesign CS4 (6.0.6)
- PDF Producer: Adobe PDF Library 9.0
- PDF Version: 1.6 (Acrobat 7.x)
- Security tab
- Security Method: No Security
- Document Restrictions Summary: All are allowed except “Document Assembly” and “Page Extraction”
- Custom tab
- Property Name “GTS_PDFXVersion”
- Property Value “PDF/X-4”
- Is the inability to save/email the document with data filled in not available with Reader X? (If so, really, what was the point???)
- If not, are there any properties of the document I can change (in Reader DC or in full Creator) that will impact the ability to save/email?
- Is there anything else that can be done to allow this user (and most of our other users) to be able to save filled in documents?
Note: I have admin rights to my machine, so I installed the updates to Reader DC when I was notified that it was available. Most of our users do not have admin privileges, and only get the updates that our IT department pushes. Therefore, updating the other users to Reader DC is, most likely, out of the question unless that's the only solution in which case we may be able to weasel our way into it.