ASP producing Adobe FDF file for PDF form population

Hello all,

I have what appears to be a simple project, but yet it's causing me serious headaches. I need to create a PDF from database data. I have the basic concepts down, but can't seem to get my FDF file to populate my PDF file.

This is my FDF file (in text)

%FDF-1.2
1 0 obj
<<
/FDF
<<
/Fields [
<</T(Recipient)/V(xxxxx)>>
<</T(Reason)/V(Taking on extra responsibilities)>>
<</T(NominatedBy)/V(xxxx)>>
<</T(ManagerName)/V(xxxx)>>
<</T(AwardDate)/V(11/04/2007)>>
]
/F(certificate.pdf)>>
>>
endobj
trailer
<</Root 1 0 R>>
%%EOF

And my PDF document contains the fields:

Recipient
Reason
NominatedBy
ManagerName
AwardDate

The PDF opens, but just doesn't fill in the data. Is there anything I'm missing, or can try, to get this to work?

Many, many thanks.
LVL 9
AlfaNoMoreAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ETA-TECHNICIANSCommented:
I ran into some of this using the collaboration tool in Acrobat.  from looking at your FDF file code, I cannot spot an error - i am not an Adobe/FDF guru.  But I can give you a recommendation in going forward.  I would defintiely download the sample FDF file that Adobe supplies for this type of FDF file.  I would use the tabbing standard they use in the sample FDF file.  And then i would compare my FDF to the sample in order to make sure it is writing exactly like the sample, with the exception of the values unique to the file.  In my experience the FDFs are very tricky and one wrong step kills the whole deal.
Nothing earth shattering here, but thought I would throw my $0.00 in.  Anyways, i hope this helps.
0
AlfaNoMoreAuthor Commented:
It would seem the problem was related to the path I was using for the /F element. I had it as a fully qualified URL, but when I tried it as a local reference (as per example), it worked a treat!

No explanation for this, as it should be fully qualified, but this doesn't work on our server! Wierd.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP

From novice to tech pro — start learning today.