What he is trying to explain is: if you want annotations to be allowed, then you must save your form as a "Adobe Static PDF form" in LiveCycle and then enable it in Accrobat pro or reader extensions. Once you do, then the dynamic properties of the form will no longer work, like buttons or subforms opening and closing. It basically becomes just like a form that you created in Word and converted it to a PDF. The first image below is a dynamic PDF with the button functioning and the new section ope...

I can send you a working module if you email me at:Jeanette@forms-and-more.rocks

What I did is, I set a button at the bottom of the form to let the user see the help page if necessary. The Help Page is set to "Hidden" in the presence on the object palette. The button itself is "Visible Screen Only" (why that's not the default for all buttons is beyond me). Then I created the Condition in the Tools/Action Builder that when the "Show Help Page" button is clicked,Page2 (the help page becomes visible) If you printed the file now, both pages would print.But since you want the use...

I set the language here:And I also insert accessibility text for each field that does not connect to the text that describes what is being asked:I don't know if this helps.....

I'm looking at your form and I have a question. I also do not write any javascript code but use the Tools section to set up a "Condition" and then a "Result".But my question is, doesn't every item in your item list HAVE or correspond to an item description? If so, this would be easier to NOT have a list box for the description and unit price but have a text field that displays the proper description for the item and price when something is chosen from the list.Or do I misunderstand the problem?

I don't know if I'm expert enough but you can contact me with what kind of help you are needing and I'll let you know if I think I can help.Jeanette@forms-and-more.rocks

I would need to see the form but I'll try and help if you will send it to me.jeanette@forms-and-more.rocks