I've been looking for a solution to this for some time...
I have several interactive forms that were developed using LiveCyle Designer 8.0. In one area I have a text box that contains instructions to the user who is completing the form. This text box object is set to "Visible (Screen Only)" so that the instructions will not print once the form is completed.
This has worked fine until recently. The form prints WITH the instructions for those users who have apparently upgraded to Acrobat Reader v9, even though the text was set to Screen Only.
The form's default properties were originally set to target Acrobat versions 7.0.5 and above. I am also now using LiveCycle ES v8.2, and re-setting this property on the forms to run under version 9.0 or later has no effect - the "screen only" text still prints.
Another behavior that has surfaced is that the "Empty Message" that I have defined for some of my mandatory entry fields and drop-down selection lists are now displaying BEFORE the user has an opportunity to enter text into the fields. Previously, these would only show if the user attempted to move to the next item without making the required entry or selection.
Anyone have any ideas? I should note that my forms are all using FormCalc.
Thanks,
DB
"... the 'Empty Message' that I have defined for some of my mandatory entry fields and drop-down selection lists are now displaying BEFORE the user has an opportunity to enter text into the fields".
I created a form with 2 rows of input fields, the remainder of the form is populated from these fields and is intended to be printed and completed using a pen for checks in the appropriate boxes and signatures where required. I made the user fields mandatory, then discovered that I had multiple error messages popping up if I should dare to try and fill in the form "out of order". I eventually removed the mandatory requirements from the fields for just this reason, and chalked it up to my inexperience with the editor!
I haven't experienced the problem with non-printable fields printing out, but this is mainly because I use the accessibility section to provide mouse-overs for each field rather than adding yet more text onto my already-crowded fillable form (I have to keep it to a single page for approval purposes), but I can see how this would also be a problem!
LiveCycle Designer 8.0
"Genius is one percent inspiration, ninety-nine percent perspiration." ~~ Thomas Edison
"If at first you don't succeed, get a bigger hammer." ~~ Alan Lewis
"If the conventional doesn't work, try the unconventional" ~~ DaveyB