5 Replies Latest reply on Oct 28, 2011 10:34 AM by JLAFARGUE

    Adobe Acrobat Aborts

    JLAFARGUE

      I'm developing a form in LiveCycle, but when I try to display it as a PDF, Adobe Acrobat aborts with absolutely no information why.  The problem is somewhere in the form's Javascript, but I could use some help in finding out where the problem is.

        • 1. Re: Adobe Acrobat Aborts
          radzmar Adobe Community Professional & MVP

          How do you open the PDF?

          Do you use the PDF Preview of Designer or do you open the file with Acrobat?

          What do you mean with abort?

          Is Acrobat closed directly or is the screen blank?

          • 2. Re: Adobe Acrobat Aborts
            JLAFARGUE Level 1

            I used the PDF Preview, then Adobe Acrobat.  Kaboom both ways.

             

            I get the message that program has encountered a problem and needs to close with a choice to send an error report or not.

            • 3. Re: Adobe Acrobat Aborts
              radzmar Adobe Community Professional & MVP

              Sounds like a precessing error.

              Save a copy of your file and remove all scripts from it and test if the problem still occurs.

              If yes, the template may be garbled and cannot be processed by the PDF Viewer.

              This may force you to rebuild the form from scratch.

              • 4. Re: Adobe Acrobat Aborts
                JLAFARGUE Level 1

                That is definitely NOT what I need to hear.

                • 5. Re: Adobe Acrobat Aborts
                  JLAFARGUE Level 1

                  I found the problem.

                   

                  At one point in the Javascript for a textbox, I had this:

                   

                   

                  if (MNPD.formStream.ND_RoutingStep == 0 && MNPD.ND_FillerPrint.rawValue != "True") {

                     ---- more code follows ---

                   

                  If you look at the first comparison, you will see that I should have been comparing the rawValue of MNPD.formStream.ND_RoutingStep to 0, not the textbox itself.   Adobe Acrobat doesn't like it when it has to compare apples to oranges.  Javascript needs a better Intellisense.

                   

                  I found the problem by eliminating fields field-by-field until I found the offending textbox, then commenting Javascript line-by-line until the offending line showed.