This content has been marked as final. Show 13 replies
You cannot edit a Designer form in Acrobat in any way. Although a
Designer form appears to be a PDF like any other, it is now a
completely different kind of thing, and the regular PDF ideas are all
Have you considered doing the form in Acrobat instead?
Hmm. That's rather disappointing. I've done a lot of work to produce the form with Designer. So far as I can see, there is no way to add a hyperlink with Designer, or I would have done it there.
You say that one cannot edit a Designer-produced form with Acrobat. I presume that you are referring to the structural items/objects in the form. One can certainly edit in terms of filling the form.
>So far as I can see, there is no way to add a hyperlink with Designer, or I would have done it there.
I don't think so. The Designer form (called "XFA") is just a PDF
wrapper round an entirely different XML format. If that format doesn't
have links, you are stuck.
> One can certainly edit in terms of filling the form.
What happens there, and in the free Reader, is that the "runtime" XFA
stuff is used. This knows how to fill in the XML form, and is quite
separate from the Acrobat form filler stuff.
Aandi - Thank you for your further reply.
As an experiment, I reconverted the original MS Word .doc file into a PDF document. I did this via Acrobat Professional 8. When the document "scanning" was complete, Acrobat automatically put me into Designer. At this point, I decided to add (in Designer) a few objects, e.g. check boxes and a drop-down list. This was accomplished successfully, so I consider that I have edited the form with Designer. I then saved the modified form (it showed Acrobat 7 Static PDF as the default format) and then opened it with Acrobat Professional 8. I then tried to add a link, and could do so. The link tool was not greyed-out. It seems to me that I have, therefore been adding a link in a form that has been edited with Designer.
Along the way in this process, I also noticed a couple of other things that are puzzling me. When I open the previous form (the real one that I am trying to develop), the existing pieces of text from the .doc file have blue rectangles around them, which can be treated as editable objects. My recent test with a new form (scanning the form from within Acrobat) doesn't result in these blue lines and the text cannot be directly edited (though the "Touch-up" tool can be used). The only difference that I can think of between the new test form and the form I am trying to develop is that the latter was converted to PDF by "printing" from Word.
The second thing that I noticed was that, after successfully creating the hyperlink, there seemed to be no direct way to give a visible title/label to the rectangle that this tool produced. The only way that I found to do this was to create a text box and place it on top of the empty link box. Is this to be expected. It seems a bit "clunky".
One thing that I am wondering about is whether I "ruined" my developmental form by enabling Reader usage rights. I cannot see any way to reverse this.
Any further help would be much appreciated. Thank you for your time.
> I reconverted the original MS Word .doc file into a PDF document.... Acrobat automatically put me into Designer.
This is not the normal path, but some form conversion options may lead
you down this path.
Normally you'd make a Word document to PDF from Word (or possibly)
Acrobat, and you can add form fields using Acrobat's form fields.
> ...Acrobat 7 Static PDF as the default format) ... The link tool was not greyed-out.
I'm not entirely clear what a static form is. Maybe it's converted
back to an Acrobat form. Can anyone enlighten me?
>the existing pieces of text from the .doc file have blue rectangles around them, which can be treated as editable objects.
This is because Designer has to essentially convert everything in your
document into form elements (static text). Doesn't happen with Acrobat
> It seems a bit "clunky".
Standard links don't allow tooltips.
>One thing that I am wondering about is whether I "ruined" my developmental form by enabling Reader usage rights. I cannot see any way to reverse this.
Save A Copy will do this.
> I'm not entirely clear what a static form is. Maybe it's converted
back to an Acrobat form. Can anyone enlighten me?
It is also a Designer form and the link tool in Acrobat is deactivated.
I am in a similar situation. Did you figure out what the solution is to add hyperlinks to a form? It seems like a serious oversight if it's not actually possible.
I don't have an original word doc to try your "workaround" solution, but since you managed to get the advanced editing tools working for a form, there must be some way to get through this...
Anyone else have any suggestions?
Jason - I gave up on using Life Cycle Designer and used only Acrobat Professional 8. I was able to do everyting I needed with that. Basically, I had to start again to do this. As soon as a file was saved by Life Cycle Designer, functionality in Acrobat Professional became limited. It's a pity, as I preferred some of the features of Life Cycle Designer.
Gordon...although you have recreated your form there is a way to add hyperlinks to a LiveCycle Designer form using scripting. Here is the link:
That's useful to know.
Indeed! Thank you. If I can pull that off it'll be my first scripting experience!
I don't understand why you can't use the link tool in Acrobat when working with a form. Especially if I'm trying to link text that's not in one of the form fields! Oh well...it's still a cool program!
>I don't understand why you can't use the link tool in Acrobat when working with a form.
You can but NOT if you have been working on a LiveCycle Designer form.
These aren't really PDF files at all; they are a new kind of thing
living inside a PDF. Every normal thing about PDFs is locked out from
If you want links and form fields you have to make the form in Acrobat
- the regular, traditional, kind of PDF form where it is still a
Well, I did what I neeeded with Acrobat Prof, so it's not really an issue for me now. It's a pity that there is this incompatibility.