I can create PDF's with editable form fields (extended features?) and serve those to our users and I can pre-fill form fields with data from the database using FDF, but then the PDF throws an error and the end user can't fill out the remaining fields (in Reader, it still works in Pro).
I've tried 2 open source approaches already, but the end result is either a fillable form or a pre-filled form. I can't seem to do both at the same time.
I've looked around adobe.com and frankly there's just so much stuff there that isn't even applicable it's staggering. I am completely lost and resorting to asking a question on a forum. I've searched these forms (and others), but anything related to this problem have no answers. I'm sure there's a way to do it.
If I try to set the PDF to fetch the FDF using a http post/submit (can I get it to do that when it loads?) I would still have to get an id number into the query string or object on a per document basis (some how?) and that means editing the PDF server side which breaks the structure which then throws the error on the client side and I'm right back at the beginning again.
At this point, it looks like it's going to take less time to simply create the form in HTML with a unique CSS file for the print version using a PNG for visual elements instead of a PDF. Not a great way to go for printing, but it would only take a day to set up. The time to create new forms is the issue. I don't want to spend 8 hours creating new HTML forms when I can do a PDF in 2 hours. Is it more efficient to go with an Adobe solution or roll my own HTML version?
All I want to do is help the users save some time by pre-filing part of the form so they can print it.
Any advice?