Apple PDF viewers barely work with regular Acroforms and don't work with
XFA forms created in LiveCycle Designer. Even the mobile versions of
Adobe Reader don't work with XFA: Adobe Reader Mobile and XFA forms from
LiveCycle Designer | Adobe LiveCycle Blog .
2D bar codes won't work with Adobe Reader, but will work with Acrobat,
so open the PDF in Acrobat to test it out. There's no such thing as
LiveCycle Reader, but for 2D barcodes to work in Adobe Reader you can
use LiveCycle Reader Extensions (Forms and extension modules | Adobe
LiveCycle Enterprise Suite 4 ) to add the corresponding usage right, but
this is not inexpensive.
Acrobat can't enable normal file attachments. It can enable commenting,
thus allowing Reader to attach files as comments, which is a manual
still has to navigate and select the file to be attached. LiveCycle
Designer can create static forms which allow this with Reader.
When you Reader-enable with Acrobat, it does not include the usage right
that allows Reader to add file attachments. Reader does allow user to
with a dynamic XFA form.
Not the end user, but the person who is distributing the form to the end
users. That Acrobat license allows the licensee to Reader-enable
documents and distribute them, but it does not allow the licensee to
sell Reader-enabled forms to someone else who distributes them.
If you want dynamic tables, you'll need to create them in LiveCycle
Designer. You can create static forms in LiveCycle Designer based on an
existing PDF, but you can't make such static content dynamic in
Reader Extensions is server-based software from Adobe that is used to
add usage rights to a PDF. These rights allow Adobe Reader to do things
it normally cannot, such as digitally sign XFA forms. Acrobat Pro can
also add the digital signature usage right at a much lower cost.
If you Reader-enabled the document with Acrobat, the form data
import/export usage right is not included. Since it's not, you won't be
Reader. You'd have to add the usage right via LiveCycle Reader
Extensions (or whatever it's called nowadays) for it to work.
It's impossible to say if support for XFA in Acrobat/Reader will be in
the future. Most non-Adobe PDF viewers and Adobe's mobile PDF viewers
have limited or no support for XFA forms, dynamic in particular, which
has been a significant problem for a while. Acroforms have significantly
more support and are part of the ISO 32000 standard, unlike XFA.
believe the XFA counterpart is.
It has been rolled into Adobe Experience Manager (AEM) Forms Designer,
which you can read more about here: Adobe LiveCycle Blog | News and
Infomation about Adobe LiveCycle Enterprise Suite and you'll find a
trial download here: Adobe - LiveCycle Developer Center | Adobe
same thing won't work with LiveCycle Designer form, but there is a forum
for it where you should ask about what's possible: LiveCycle Designer
There is no type of check box that behaves that way. You can fake it
http://acroscript.net/pdf/demos/multistate_4.pdfYou'll have to study it
to see how it works. Note that you can only rely on this technique
working with the desktop versions (Windows/Mac) of Adobe Reader and
Acrobat, not other PDF viewers, mobile viewers in particular.
You don't need Acrobat, your client does. It's far less cost than
LiveCycle Reader Extensions, which would have been the only option
before Acrobat DC was available. Licensing costs can be as low as
$14.99/month. So if their need is limited, it can be done for very
You can't use Reader, you have to use Acrobat. So your client will have
to get Acrobat and Reader-enable the forms that you develop. If you
don't have Acrobat, you can download and install the trial version so
you can test this out.
An option is to Reader-enable the form with Acrobat DC. It doesn't have
the licensing restrictions related to enabled documents that previous
versions do. You won't be able to Reader-enable documents for your
client with Acrobat, but your client can.