SOLVED
If I use adobe reader 7.0 to open LiveCycle Designer ES2, what will happen?
1 Accepted Solution
Correct answer by
Hi,
When you design a form in LC Designer ES2 you can set the target version of Acrobat/Reader in the File > Form Properties > Defaults tab.
While you can target v7, you need to be aware that some of the functionality in LC Designer ES2 is not supported in Reader v7. For example in LC Designer you can set the presence of an object to 'visible (screen only)', but this is not supported in Reader v7, so would cause a problem. So for each form you would need to set the target version and then check the Warnings palette to see if there are any problems.
Check out the post by John Brinkman discussing Acrobat X, as this has a very handy table for the LC Designer/XFA Specification and Acrobat/Reader versions: Acrobat X and XFA 3.3
| XFA Version | Acrobat/Reader |
| 2.1 | 6.02 |
| 2.2 | 7.0 |
| 2.3 | 7.0.1, 7.02 |
| 2.4 | 7.0.5, 7.0.7 |
| 2.5 | 8.0 |
| 2.6 | 8.1, 8.1.1 |
| 2.8 | 9.0 |
| 3.0 | 9.1, 9.2, 9.3 |
| 3.3 | 10.0 |
You can see there are alot of changes around v7 and that if the user has Reader v7.0.7, then you can utilise the features in XFA Specification 2.4.
The other issue to be aware of is that users with Reader will NOT be able to save data in the form UNLESS the form has been Reader Enabled before the form is deployed.
The form can be Reader Enabled in two ways:
- Using Acrobat Standard v9 or Acrobat Professional v7 or v8. Has licence restrictions, see EULA.
- Using a server produce called Adobe LiveCycle Reader Extensions ES2. Additional costs.
Here is a summary of the options available to users with Reader, depending on whether the form is Reader Enabled AND how it was enabled:
There is a post here and a PDF summary:
http://assurehsc.ie/blog/index.php/2010/05/using-livecycle-forms-in-acrobat-and-reader/
Hope that helps,
Niall
Correct answer by
Hi,
When you design a form in LC Designer ES2 you can set the target version of Acrobat/Reader in the File > Form Properties > Defaults tab.
While you can target v7, you need to be aware that some of the functionality in LC Designer ES2 is not supported in Reader v7. For example in LC Designer you can set the presence of an object to 'visible (screen only)', but this is not supported in Reader v7, so would cause a problem. So for each form you would need to set the target version and then check the Warnings palette to see if there are any problems.
Check out the post by John Brinkman discussing Acrobat X, as this has a very handy table for the LC Designer/XFA Specification and Acrobat/Reader versions: Acrobat X and XFA 3.3
| XFA Version | Acrobat/Reader |
| 2.1 | 6.02 |
| 2.2 | 7.0 |
| 2.3 | 7.0.1, 7.02 |
| 2.4 | 7.0.5, 7.0.7 |
| 2.5 | 8.0 |
| 2.6 | 8.1, 8.1.1 |
| 2.8 | 9.0 |
| 3.0 | 9.1, 9.2, 9.3 |
| 3.3 | 10.0 |
You can see there are alot of changes around v7 and that if the user has Reader v7.0.7, then you can utilise the features in XFA Specification 2.4.
The other issue to be aware of is that users with Reader will NOT be able to save data in the form UNLESS the form has been Reader Enabled before the form is deployed.
The form can be Reader Enabled in two ways:
- Using Acrobat Standard v9 or Acrobat Professional v7 or v8. Has licence restrictions, see EULA.
- Using a server produce called Adobe LiveCycle Reader Extensions ES2. Additional costs.
Here is a summary of the options available to users with Reader, depending on whether the form is Reader Enabled AND how it was enabled:
There is a post here and a PDF summary:
http://assurehsc.ie/blog/index.php/2010/05/using-livecycle-forms-in-acrobat-and-reader/
Hope that helps,
Niall
Related Conversations
