stefan_nygren

It seems we have a big challenge to solve our need!?

1. We need to populate a PDF with data from a database
2. Programatically set the user rights on the resulting PDF so that the user can add data and save the file locally.

Tecnically this seems possible with OpenSource solutions but it appears that Adobes licensing in Acrobat Reader prohibits us from doing this, hereby forcing us to use an Adobe product for this!?
"The EULA for Adobe Reader now forbids enabling features found in Acrobat except via files enabled via licensed Adobe Reader Extensions. This, it has been argued, would prevent third parties reverse engineering the system and offering alternative software since the end users would be in a situation of license violation".

If this is true we need to do this via an Adobe product. Please give us hints how to solve this without violating any licensing rules.
The solution will be implemented in our software and spread to our customers. It is only 3 source PDF's involved and approximatelly 400 end users of the source. But of course we have no control of how many times they use the source PDF, i.e. how many filled & saved copies there will be in the end.
Is it at all possible to this programatically with an Adobe product (Acrobat professional or Live Cycle Reader Extensions).

Any input on this will be greatly appreciated! Help!!

aandi_inston

That appears to be the prevailing intepretation. Look at it this way:
if this technology was freely implementable, the whole Reader
extensions concept has no point: the only point is to sell Adobe
products, to replace Adobe's revenue stream for people who would
otherwise have purchased Acrobat for their end users in order to do
the extended features. If it wasn't for the concept, Reader would
simply not do these things at all.

The only product available is LiveCycle Reader Extensions (name may
have changed). Acrobat has no API to do this. Note that Reader
Extensions isn't a simple retail product; the price is negotated with
each client according to their expected use.

Your solution is open source? That shouldn't be a problem, you can
write software that interfaces to LiveCycle Reader Extensions, and
therefore fails if the customer hasn't purchased it.


Aandi Inston