> they're just standard form fields
Okay, that's easy enough to figure out.
> The client could see a link to a prepopulated fdf file, or they could
> see a link to cfm template that serves up the fdf file via cfcontent.
> Inside the fdf file is a link pointing back to the pdf file.
Which, if I'm understanding you correctly, just opens the PDF that the FDF
file "points" to, and in the person's browser window, they see the PDF with
the populated form data.
> > And if she has Acrobat Pro, she can just "save" it?
>
> You can save the FDF file which when clicked will open acrobat and
> populate the remote pdf form with data. I don't know if you can save
> the pdf file with the data stored in it or not. I don't have acrobat
> here to test it.
I think *that's* the difference between "Acrobat" and "Acrobat Reader". If
you have "Acrobat" you can save the PDF with the form data intact, and
rename it something else. If you have Reader, you can save the form, but
when you open it up wherever you saved it, it doesn't retain the populated
form data. Or at least that's been *my* experience.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
