Skip to main content
Participant
February 24, 2025
Question

form print button

  • February 24, 2025
  • 1 reply
  • 310 views

Hi, attached pdf form was sent to me by my bank.
I filled it out on a computer, then printed it by printer dialogue, signed it by hand, scanned it and sent the scan by email back to my bank.

The receiver said the form only can be read correctly by him, if I print the document by the "print" button embedded in the document itself (top left corner)
I tried various pdf readers, some showed me 4 embedded buttons at the top of the pdf page (Foxit, if I remember corretly), some only one, and some (Brave browser) displayed that the document needs Acrobat Reader 8 or higher, although the Acrobat plugin for chrome is up to date.
Acrobat reader is also up to date (ver. 24.005.20414), in each program tht's able to display the document, be it with 4 or only 1embedded form buttons, none ofthe buttons do anything when clicked.
I haven't any printers installed, but at least a printer dialoge should pop up, no? (to export the filled document as a new pdf would be my plan, then print this pdf in my office)

Is the document itself broken, or what is it?

(I asked the bank person what's wrong with the printed-out document that I sent them, but they just repeated what they said earlier)

1 reply

Thom Parker
Community Expert
Community Expert
February 24, 2025

This is a dynamic XFA form, not a PDF. It can only be viewed correctly in Acrobat.  I'd only used in in the latest Acrobat DC.   

The problem is with document, there is an error in the print script on the button. 

However the script is simply trying to execute the print menu item.  So try printing it from the "File->Print" menu item. 

You probably are using the new Acrobat UI. To make this process easier, revert to the old UI.

 

 

 

 

 

 

 

Thom Parker - Software Developer at PDFScriptingUse the Acrobat JavaScript Reference early and often
try67
Community Expert
Community Expert
February 24, 2025

Were you able to examine the button in LCD? I see that the error is caused in line 6 of the button's code, so there might be other things happening in the background there...