-
1. Re: Interactive PDF - some can't type into fields
Damon Edwards Jan 20, 2010 9:42 AM (in response to Damon Edwards)This problem still exists, and its a large well known company who is being burned by this. Very sad not one response from an employee.
-
2. Re: Interactive PDF - some can't type into fields
MichaelKazlow Jan 20, 2010 6:16 PM (in response to Damon Edwards)This is not a conduit to technical support, but a user to user forum. If you want technical support you need to call Adobe and pay a fee.
-
3. Re: Interactive PDF - some can't type into fields
Damon Edwards Jan 20, 2010 7:16 PM (in response to MichaelKazlow)I was referred here by phone support, but thanks for being helpful.
-
4. Re: Interactive PDF - some can't type into fields
~graffiti Jan 20, 2010 8:00 PM (in response to Damon Edwards)Could be anything. It would help if you could post one of the PDF's that you know is a problem. Plus it would be good to know what exactly happens when they try to type in to the fields and how they are opening the file (within a web broswer by clicking a link, saving to hard drive then opening Reader and using File>Open...etc.).
-
5. Re: Interactive PDF - some can't type into fields
Damon Edwards Jan 21, 2010 2:08 PM (in response to ~graffiti)Here's the process we finally deduced as a working model to keep the interactivity working for everyone. After we made a type change on the pdf, we needed to: File->Save a copy, then open that copy and do Advanced->Preflight, then Advanced->Enable usage rights.
-
6. Re: Interactive PDF - some can't type into fields
~graffiti Jan 21, 2010 6:17 PM (in response to Damon Edwards)Advanced>Preflight? For what purpose? I guess I don't grasp that step (plus that is just the beginning. There are numorous things that can be done in pre-flight.
-
7. Re: Interactive PDF - some can't type into fields
Bernd Alheit Jan 22, 2010 3:51 AM (in response to Damon Edwards)May be that the users has activated the PDF/A mode.
-
8. Re: Interactive PDF - some can't type into fields
gozargozarian3 Jan 27, 2010 9:01 AM (in response to Damon Edwards)We started experiencing this at our company after the most recent update to Adobe Reader. Maybe it had something to do with that?



