Thanks for posting your form and it works great.
However, when I try to implement only part of your form (dropdownlist with binding emails, Fake email Button with Click event and invisible RealEmail button) with LifeCycle Desiger ES 8.2, it just didn't work when opening it in Reader. Is it because I don't have Reader Entensions?
Is Acrobat Pro able to achieve same function without using Reader Extension?
If the user has the full version of Acrobat, then the email button will work. This is because the email button saves the form first and then attaches it as a PDF to the email.
Because users with Reader cannot normally save a form, the email button fails silently.
There are two ways to reader enable a form to allow users with Reader to be able to save the form (and therefore allow the email button to work):
Here is a summary of features that are available depending on whether the form is enabled and how it was enabled: http://assurehsc.ie/blog/index.php/2010/05/using-livecycle-forms-in-acrobat-and-reader/
Another option is to set the email button to return the data as a XML file (instead of PDF). Users with Reader can achieve this without Reader Enabling the form.
Thank you very much for your reply, Niall.
I could Reader enable Paul's form and my form in Acrobat Pro. While Paul's form can be saved and the email button works with Reader, my form CAN only be saved in Reader but the Submit (email) button has no response.
Based on your chart, my form should be able to be submitted. Where might be the problem?
BTW, submitting Pdf form is preferred in our situation.
It looks like the script is referencing an object called "DropDownList1", but that this object either:
- does not exist;
- exists, but has a different name; or
- exists, but DropDownList1 is in a different subform to that of the button.
When referencing an object you need to give a sufficiently full reference.
Thanks for your immediate response, Niall.
I tried to compare what Paul did with mine. Seem I did exactly the same thing except that my form Hierarchy looks messy whereas Paul's is very clean.
Should I clean my hierarchy to make it look more like Paul's? Right now I have many Paragraphs in Page1 (DropDownList1 and the buttons are on different Paragraphs) but I only have one subform which is the TopmostSubform. Any references for cleaning the Hierarchy?
Sorry for the trouble.
First off, it looks like you created multiple subforms called 'Paragraph'. LC Designer keeps track of the various instances of these using a zero-based instance number Paragraph. This is OK, but makes referencing objects more difficult, because LC has to resolve the node for the object.
So I would recommend that you name objects (subforms, fields, etc). So that you can easily reference them in script.
TopmostSubform is the name of the root node. This name indicates that you imported an existing Word document or PDF to start off the form. This is OK, but some of the normal LC functionality will not be available.
The DropDownList1 object is in the second instance of the Paragraph subform. Therefore if you button is on Page1, it will need to include the subform name in its script.
For example if you left the names as they currently are (several instance of the same name), the script would look like this:
But if you gave the subforms a unique name the script would be much easier, say 'myParagraph':
Hope that helps,