Printing Dynamic Form PDF causes data loss

[msmamet@adobeforums.com]

I have a PDF that I created using Acrobat 4.0
I took an existing Word Document and created a PDF from it.
I then went in and added form textboxes to the new PDF.

On my web site I have an ASP page that writes an FDF file that reads data from a SQL Server database and populates the acrobat fields in the PDF on the browser (IE w/Reader 6.0 ).

this setup has been working for years (since back when Acrobat 4.0 was the latest version). I recently added a few more pages to the PDF file and now I'm encountering problems.

When the PDF opens in the Browser w/Reader 6.0 it displays all 16 page like I expect. The Data is visible on the pages. However, when I print this I get unexpected results. Some fields are left blank. If I print the same form multiple times, the fields that are left blank are not consistent. Some whole pages of dynamic data are left blank, some pages are half populated, etc.

Can anyone think of why this might be happening?

-
Matthew

[Bernard_Andrew@adobeforums.com]

Matthew:
I apologize in advance for going off-topic here, but I was hoping to get your help.

<<When the PDF opens in the Browser w/Reader 6.0 it displays all 16 page like I expect. The Data is visible on the pages>>

Are you using a JavaScript to import your FDF data into the corresponding form fields?

My problem:
I have my XFDF data file, saved into the same directory as my PDF's (4 total) - with properly corresponding forms (and No Security applied), I have set a Page Open/JavaScript:

setDisclosed()
{this.disclosed = true;}
setDisclosed();
this.importAnXFDF ("mydata.xfdf");

In Full Acrobat 6.01, the PDF's open, and import the XFDF data perfectly into all 4 PDF's. Works exactly as I had hoped.

However, in Reader (6.01), it's as if the JavaScript doesn't run, and the data does not get imported. Am I missing some major pieces of the puzzle here? Am I possibly trying to implement a JavaScript that won't work with Reader?

Again, I apologize for not addressing your posted issue.

Thank you for your help!
Bernard A.

[Bernd_Alheit@adobeforums.com]

Bernard,

you should read the Acrobat JavaScript Guide. The method importAnXFDF requires advanced Forms Features rights to work with Adobe Reader.

[Bernard_Andrew@adobeforums.com]

Bernd:
Thank you for responding. I think I'm in error in misreading the information in the manual.

On p.169 in the Acrobat JavaScript Scripting Reference, importAnXFDF section, it displays 5.0 compatibility; white cicled D, indicating that using this property dirties the PDF (p.21, same manual); and black circled F, indicating requires Advanced Form Features rights (also p.21).

So, I thought that applying Document Properties, such as including Filling of Form Fields Allowed, isn't really what I want to do.

What I want is the menu selection Advanced Form Features - in which Import Form Data resides,, which of course don't apply to Reader. I understand that, now. And it seems fairly clear that there isn't any way to circumvent that (by running a JavaScript to Import that data into the setup forms in Reader). A 3rd party plug-in, perhaps?

So, how does Matthew accomplish this then? Just guessing here: his ASP page generates a specific FDF based on the user's information, then launches that FDF so that it populates his PDF, thereby creating a PDF specific to that user's FDF.

Does that sound correct?

Sorry if I rambled here, just wanted to make it clear as mud in my own mind. :-)

Bernard A.

[Bernard_Andrew@adobeforums.com]

Sorry about the double post, folks. I wanted to try and clarify something.

* ****************** Again, the Acrobat JavaScript Scripting Reference page 22, Column 4 Availability in Adobe Reader section, states:

• The property or method can be accessed only in the Adobe 5.1 Reader depending on DOCUMENT rights.

Then, the very next line states for black circled F:
• requires Advanced Form Features RIGHTS

That is why I thought that applying Document rights, such as including Filling of Form Fields Allowed would let me import my XFDF into the PDF, even in Reader, via the JavaScript call.

For my case, is it really not Document rights I want, it's application rights/functionality provided solely by Acrobat Pro?