If my “fixed page form” you mean the case where your imported form becomes the background and you put fields over top, then no, you cannot use fragments with this type of document.

Fragments can only be used in flowable layouts (i.e. dynamic forms).

I am working on a large conversion process (3500+ forms), I’ve decided that I dont need the full functionality of an XDP and am converting these forms to a Fixed Page form. My question is simple, can I still use fragments on a Fixed Page form?

Thank you for taking the time to give some valuable feedback. It’s very much appreciated and I’m sorry the new version is proving troublesome for you. I would recommend installing Service Pack 1 for Designer 8.2 which should at least help with the stability issues.

I’ll make sure your feedback gets to the team. Would you be able to send me your form? It would help to have it along with your feedback so that we can try to reproduce those bugs on our end. Please send it to “formcollateral1 /at/ stefcameron /dot/ com”.

Finally, you can always report bugs on Adobe’s Wish List.

I’ve just recently upgraded my Web Premium package to CS4 and I was really looking forward to LiveCycle 8.2.1 mainly because of the new tab order feature. Well, it’s not all as I had hoped and here’s why:

Most of the dynamic forms I create are pretty advanced with scripting. One in particular I’m having trouble with has 80-112 fields on a page and is 4 pages long. Creating this form has been a battle for a number of reasons, writing Adobe’s version of JavaScript, the program crashing, and setting the tab order, being some. I first experienced LiveCycle 8.0, and was really looking forward to some of the new features with 8.2 (with Acrobat’s 9 release). I was also hoping that there would be less bugs in 8.2, but now I’m finding new bugs.

Working with so many fields on a page, setting the tab order is very important. I have subforms that are hidden, and based on the answer in one subform makes another subform appear, needing to tab to that field and continue regular sequence. Well, in order for that field to even show up in the Tab Order hierarchy, it has to be visible? Well, some are showing and some aren’t, hence one of the bugs.

So I’ve made all my hidden fields visible so I can set the tab order. I start moving fields around to create my custom tab order, and things seem to be working well, except when I want to move the buttons that are at the top of the list, to the bottom. My whole tab order sequence got mixed up. So instead of moving that one field to the bottom, I decided to try to move ALL my fields to the top and it worked – a work around the bug. Weird work around, but it worked.

Move on to the next page. Started setting my tab order, and the first page got out of order. HUH?! Why would changing the tab order on the 2nd page mess up the 1st page? Now I’m getting frustrated. I’ve been spending 2+ hours trying to set the tab order (even more researching if there were any fixes or work arounds I didn’t know about) on this form which is RIDICULOUS. There should be an easier, non-buggy way to do this, right?

Also, now I CAN’T set a field to NOT be a part of the tab order. Why would Adobe take that away in 8.2? That was a nice feature that I used frequently and now a user HAS to tab to EVERY field within a form? That’s a bit absurd. 8.2 is no less frustrating than 8.0, and with the program crashing on me and these bugs I’ve mentioned, even more frustrating and disappointing. How can I set my tab order on this form? Am I missing something? Or do I need to keep waiting for another release and hope that the bugs are fixed again? I can’t believe that Adobe would brag about how cool their fillable forms are, and then have a quirky program to try to create them.