Avatar of bcolladay
bcolladayFlag for United States of America asked on

Open a PDF from webserver Let user fill online then save back to webserver

ASP.net C# Developer, I would like to open a user specific PDF stored on a web server, the user could then fill out the PDF as a fillable form. When they are done, they would click a save button and the form, along with what they typed in the blanks would be saved back into the user's directory on the webserver.

I don't need or want to save the form field information, just the filled out form itself.

Can this be done with simple C# asp.net tools? I know of some off the shelf programs that do something like this, just hoping there is an easy I/O way to get it done.
DatabasesAdobe AcrobatDocument Imaging

Avatar of undefined
Last Comment
Scott Fell

8/22/2022 - Mon
Scott Fell

When you create a form in acrobat pro, you can program where the data goes.  In the form designer, create a button. Then on the button properties, go to Actions.  Use the "Select An Action" drop down to Submit a form. Click the Add button from there you get a pop up for a url to submit the form data.    You would use your .NET code to collect the form data and update the db.  

If you want the form saved as a pdf, you would change the action item drop down from submitting a form to a menu item and choose Save As.  Then you would need to instruct your user to upload the pdf and use your .NET page to accept the upload and save it.
ASKER
bcolladay

It is the second part that I am wanting, except what I want is someway to do this automatically so the end user doesn't have to upload something.  

So in my mind: The end user would click on a link that maybe opens the pdf in an iframe and outside the iframe in the web page there would be a "save" button. When the save button is clicked, the filled-out form is saved back on my web server as a pdf with the information they typed saved as well.

I don't want to save the data from the form and I don't want to rely on the user to upload the correct file.
ASKER CERTIFIED SOLUTION
Scott Fell

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER
bcolladay

I believe you are correct. Just wanted to see if I had missed anything. This is for a medical portal, that has several, more than 20, clinics, they all have their own forms (5 - 15 per clinic) for new patients, medical history, etc.

Right now all I do is open their .doc files, convert them to fill-able form pdfs and upload them. They are all unique, so I am wanting to avoid parsing the data or recreating the form for each clinic.

The best work around is the print to pdf / save pdf and have them upload it. I just don't think end users read or follow instructions very well. I think most of them are unwilling to do this. I will talk to my clinics and see if this is an acceptable method. SO many browsers and so many versions of Adobe Reader.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
ASKER
bcolladay

Not what I was hoping for but I believe it to be accurate.
Scott Fell

For the type of info you are gathering, it would probably be safer to store the data to a db rather then the entire form anyway. Then just recreate a pdf programmatically when needed.  At least with storing data to the db you can encrypt it and it does not take up as much space.  With documents, you have to upload to the server, then use your scripting to move the document outside of the www so it can not be accessed accidentally.