Will the users each own Adobe Acrobat? (I think that might be a prerequisite)
The documentation on this functionality is misleading. It says you only
need "Form Rights" to do it in Reader, but the rights that you can apply in
Acrobat are not sufficient for that. You need the LiveCycle Reader
Extensions Server to get it working in Reader.
The chances are that buying Acrobat for the users is the most cost effective way to achieve the functionality you specify.
If you are prepared to use the normal form workflow - where forms are submitted to a web server (not emailed!) you can have an FDF submitted with no special rights, and with Reader.
As I said, I am VERY new to programming for Acrobat.
As a matter of fact, this is my first attempt.
I hate to be stupid about this, but I do not understand the rights issue here.
Perhaps it would help if I explained what I am doing.
I am trying to fill in PDF forms such as this one: http://www.vba.va.gov/pubs/forms/VBA-27-2008-ARE.pdf
Is it possible to modify this form using Acrobat to enable it to export the data to FDF when the end user has only Reader on their machine?
That is really all I need to know.
Thanks a million (before taxes)
This is not a server application.
It is a desktop application.
I just need to have the FDF exported to the local machine when Reader is closed.
Thanks for the help.
Without applying a special right with an expensive product, it's not possible.
Thanks for the information.
Is this true?
It does not allow me to type anything into it.
Is there a “document.close()” event that I can hook into?
I did not see it in the object list.
LiveCycle Designer is a different product to LiveCycle ES (the server engine). Designer cannot apply LCRE extended rights to a form, it just does the page design.
LiveCycle ES runs on dedicated server platforms, and typical licenses run into five figures USD. It's designed for enterprise customers only.
Also, LiveCycle Designer makes an entirely different kind of form, which can only export XML, not FDF at all. Definitely not what you needed.
I can live with exporting XML. The export does not have to be in FDF format.
OK – thanks for the quick response.
I had to exhaust all possibilities before giving up on this.
I hate to be stupid about this, but I am just learning about this stuff.
I read this in the documentation for the Adobe Acrobat SDK:
Importing and exporting form data
Form data can be exported to a separate file, which can then be sent using email or over the web. When doing this, save either to Forms Data Format (FDF) or XML-based FDF (XFDF). This creates an export file much smaller than the original PDF file. To programmatically save your data in one of these formats use the Doc object methods exportAsFDF and exportAsXFDF. On the server-side, use the FDF Toolkit to read the FDF data, or use a XML parser or library to read the XFDF data Note that Acrobat forms support the FDF, XFDF, tab-delimited text, and XML formats, and that XML forms support XML and XDP formats.
Are you saying that I need to have LifeCycle ES installed in order to do this?
Not necessarily. First, you should understand that what you read there has no mention of the limitiations of Adobe Reader. Adobe want to sell Acrobat or other software, and it is probably the single most common error people make in this area to assume that whatever it is that suits their business to do for free with Reader will be allowed by Adobe. (Who have the upper hand here).
But let's look at what you quote. This is exactly what I was referring to in reply #4: submit the form, just like every HTML form in the world, countless millions of them.
Form data can be exported to a separate file, which can then be sent using [email or] over the web. ... On the server-side, use the FDF Toolkit to read the FDF data, or use a XML parser or library to read the XFDF.
Thanks so much for staying with me on this.
I understand that reader has an extended option to export data as XML.
I do not want the users to have to click a button to do this.
I want to do it automatically when reader is closed.
If Reader provided an automation interface I could do this easily, just like I do when automating Excel, Word or QuickBooks.
Is there any way to accomplish this in a desktop application?
Marcia G. Akins
<http://www.tightlinecomputers.com/> Tightline Computers, Inc.
Have you thought about how to handle the action if no fields are completed or there are required fields left empty?
If you create the form in LiveCycle Designer then you should try to keep all actions for the form within that product. You could use the docClose action.
If the fields are empty, it is not an issue.
My problem is that this is a government form that I am trying to modify so that I can extract the data back to my application.
When I open the form in LifeCycle designer, I cannot enter anything in the script editor.
I have a feeling that this is because I did not create the form.
Is this the case?
When I open the form in the designer, it tells me that it was set to a lower version than 9.0 and LifeCycle Designer ES no longer supports the version.
It then goes on to talk about setting defaults in the Form Properties dialog box, but I have no idea how to get into this dialog box even though I have searched for it.
There's a logical reason why official documents issued by government agencies aren't easy to edit - they don't want people using them for phishing.
Create your own form from scratch, set up a simple website to receive the XFDF data packet, and you're good to go. If that's too much effort, then you really need to re-think the purpose of your project. Look at FormsCentral or surveymonkey.
Well, I finally figured out how to get into the script editor.
But I can’t find a method to use to export to XML L
With LiveCycle you can use FormCalc and the exportData method
For security reasons, if you provide the first parameter, the exportData method executes only when performed on certified documents. If you do not provide the first parameter, the document does not need to be certified and the user is prompted to provide a location and file name.
Reference_Syntax.exportData( [ STRING param1 [, BOOLEAN param2 ] ])
Specifies the location and file name of the file where the data will export. If you omit this parameter, a dialog box opens to let the user select the file manually.Note:
To change the export type without specifying a file name, you must provide an empty string as the first parameter. For example:
xfa.host.exportData("", 0) //FormCalc