Using Adobe Acrobat 9.4.1 Std and Win 7 32bit
I have created a form and gone through the Distribute process, selecting the manual method of attaching the form to an email and collecting responses in my inbox. I've set the returning email address and the response tracking file. To test I have attached the form to an email going to another computer and email address in my home. After completing the form and hitting the submit button a window pops up showing the TO address and asking for the FROM email and name. Then a second window pops up asking to chose 'desktop client' or 'Internet client' and I chose Internet client. Then comes a 'save' window asking where to save the form. After selecting a folder and clicking save, the completed form saves and the box closes. Then NOTHING happens--the form is not sent, as I understand it is supposed to do. I don't want to have to ask the 150 recipients to send the form back via a separate email an attachment.
I have tried enabling usage rights in Adobe Reader but that doesn't change anything. Most of the people to whom the form will be sent will not have full version Adobe Acrobat, but will have Reader instead.
I do have the option of posting the form on our website and sending a link, but I'm guessing that I'll have the same issue.
Forms cannot be submitted
2011-01-09 13:35:56
My Product Information:
Acrobat Standard 9.4, Windows
Acrobat Standard 9.4, Windows
2011-01-10 15:48:32
#2
Thanks. This is frustrating. I did finally figure out that the forms would have to be emailed back as an attachment. But my problem now is that those with Adobe Reader cannot save the form so they can attach (well I should say, some with Adobe Reader cannot save). When I send it to my husband's computer (with Reader only), it works fine. But others can go through all the steps until they get to the SAVE AS window and then they get this error message: "Acrobat could not open the file "". Detailed error: A file error has occured"Any ideas? This happens whether I send the form as an attachment or as a link to the form posted online.
Thanks again.
Thanks again.
2011-01-10 16:00:37
#3
Quick Question:
You Stated: "I do have the option of posting the form on our website and sending a link, but I'm guessing that I'll have the same issue".
Do you have a Microsoft Server OS web server?
If so, try a Microsoft .net solution called PDFEmail.net.
How PDFEmail.net works:
Install PDFEmail.net on a client workstation, and configure PDFEmail.net with the SMTP, Message, Response settings.
PDFEmail.net creates server-side ASP.net scripts and DLLs without any programming knowledge.
Set the PDF form's submit button action URL to point to the script on the remote Microsoft web server.
Upload your scripts and your PDF to your server, and distribute the blank PDF or distribute a link to the PDF.
Notes:
E-mail submissions are sent via server-side script, without Client Side E-mail Software such as Outlook.
PDFs can either have "Usage Rights Enabled" and the client submits the whole PDF (Raw format). Or the PDF's can be submitted by sending FDF(Acroform), XDP (LiveCycle), XFDF(Acroform/LiveCycle), or XML(Acroform/LiveCycle), and then the data can be merged with bacl with a blank PDF form and attached to the e-mail. Or the data can be sent with FDF(Acroform), XDP (LiveCycle), XFDF(Acroform/LiveCycle), or XML(Acroform/LiveCycle) formats.
ASP.net Scripts can be reusable, by passing query string variables to the the URL.
ASP.net Scripts can be easily modified to save to database, or file folder system.
ASP.net Scripts and Binary DLLs are fully redistributable, and can be used on more than one server.
PDFEmail.net is licensed per developer, free support and updates included for one year.
PDFEmail.net uses iTextSharp technologies.
Useful links:
PDFEmail.net
NK-Inc.com
FDFToolkit.net
You Stated: "I do have the option of posting the form on our website and sending a link, but I'm guessing that I'll have the same issue".
Do you have a Microsoft Server OS web server?
If so, try a Microsoft .net solution called PDFEmail.net.
How PDFEmail.net works:
Install PDFEmail.net on a client workstation, and configure PDFEmail.net with the SMTP, Message, Response settings.
PDFEmail.net creates server-side ASP.net scripts and DLLs without any programming knowledge.
Set the PDF form's submit button action URL to point to the script on the remote Microsoft web server.
Upload your scripts and your PDF to your server, and distribute the blank PDF or distribute a link to the PDF.
Notes:
E-mail submissions are sent via server-side script, without Client Side E-mail Software such as Outlook.
PDFs can either have "Usage Rights Enabled" and the client submits the whole PDF (Raw format). Or the PDF's can be submitted by sending FDF(Acroform), XDP (LiveCycle), XFDF(Acroform/LiveCycle), or XML(Acroform/LiveCycle), and then the data can be merged with bacl with a blank PDF form and attached to the e-mail. Or the data can be sent with FDF(Acroform), XDP (LiveCycle), XFDF(Acroform/LiveCycle), or XML(Acroform/LiveCycle) formats.
ASP.net Scripts can be reusable, by passing query string variables to the the URL.
ASP.net Scripts can be easily modified to save to database, or file folder system.
ASP.net Scripts and Binary DLLs are fully redistributable, and can be used on more than one server.
PDFEmail.net is licensed per developer, free support and updates included for one year.
PDFEmail.net uses iTextSharp technologies.
Useful links:
PDFEmail.net
NK-Inc.com
FDFToolkit.net
2011-01-10 16:10:43
#4
Boy! That is above my head. I'll send this to my web guy and see if he can help!
Thanks
Thanks
2011-01-10 16:20:51
#5
If the PDF has Save Rights then it should be able to be saved with Reader. But there are a couple of things that can go wrong. First, Rights applied with Acrobat 9 are not good on all versions of Reader. It might not work well on 6 or 7, but I'm pretty sure it will work on 8 and 10. It should definately work on 9. Second, Rights can be invalidated by certain kinds of changes to a form. Something as simple as a script that changes the color of a form field can cause problems. And versions of Reader other than 9 are more sensitive to this sort of thing. Field value changes should be ok, but you never know. Other problems with enabled forms have been reported on this forum.
Another issue is that you are using Acrobat Standard. I'm not sure what the extent of Rights Enabling is for that variation. I actually didn't think it had the ability to distribute forms.
I'd suggest creating a very simple form and putting it though the distribute process. Then repeating your testing. If the simple form works well there is probably an issue with the full form that's invalidating the rights. If it doesn't works then there is something intrinsically wrong with your process.
Another issue is that you are using Acrobat Standard. I'm not sure what the extent of Rights Enabling is for that variation. I actually didn't think it had the ability to distribute forms.
I'd suggest creating a very simple form and putting it though the distribute process. Then repeating your testing. If the simple form works well there is probably an issue with the full form that's invalidating the rights. If it doesn't works then there is something intrinsically wrong with your process.
2011-01-10 18:16:44
#6
I will try that just for my own knowledge. I've decided that too much can go wrong with using this method to get out my surveys to the entire group. I would have no idea what version of Reader all 150 of them have. AA 9 Std does have the ability to make and distribute forms--that is one reason we purchased it to begin with. It had many of the features that we wanted in 8 but didn't have. Obviously we haven't used the form feature before now. Thanks for trying to help. I'll keep working on it.
Kaye
Kaye
The issue has nothing to do with where the form is posted or enabling rights for Reader. The issue is that Acrobat does not support the web mail protocol. If a system does not have a MAPI email client then Acrobat asks, which it did. If internet client is selected Acrobat saves the form locally and you have to manually attach it to the email using your email program. I believe all the instructions are in the popups.
This is an awkward process that confuses many users. Emailing forms has always been considered a bad idea for this very reason. And especially now since many people use web mail clients. There are some good alternatives to emailing a form. The easiest is to use Acrobat.com for form data collection. You could also purchase a 3rd party form data service, such as www.formrouter.com. Or you could write a server script to do the data handling, which is the traditional best solution.
BTW: if you put the form through the "Distribute" wizard, then it is already enabled with Reader Save Rights.
Thom Parker
The source for PDF Scripting Info
www.pdfscripting.com
Very Important - How to Debug Your Script