I fixed the problem without code by grouping sections within the PDF that had either western or top-down flow for data entry, and then wrapping each group in a subform. At first I tried to set each subform with a specific tab flow (western or top-down), but that didn’t work. Leaving all the subforms as positioned, however, did accomplish what I was looking to do.

Steve

I’ve been wrestling with this problem for a while, and thought I might seek out help from a pro. Can you programmatically control tab order through a script? I ask this because I have a form that uses a button to add a new instance, and I have set a custom tab order for the 21 fields on the form. Problem is, when I click the add button to add a new instance, the tab order reverts to its default setting. I need it to maintain the custom order when I add a new instance. Any ideas for how to handle this? Thanks for any assistance or guidance you can provide.

Steve

It looks like there’s a forum for Reader Extensions in LiveCycle 6.x and 7.x, in case that can help, but there isn’t one for LiveCycle Reader Extensions ES.

I really don’t know what to suggest, unfortunately, and I don’t know of any online resources, other than documentation on LiveCycle Reader-Extensions and LiveCycle Forms, where you might find the answer you’re looking for.

Fortunately for you, when I inquired to my colleagues about your problem, they asked if they could have a look at your form to better understand what’s going on. If that’s possible, can they contact you via the email address you used when you posted your comments to my blog?

I would guess that it’s the same order as initialization order but it’s easy to test: Just download my sample form and do the same thing I did for the Initialize events on every object’s Form:Ready event and preview the form. Then look at the output in Acrobat’s JavaScript Console.

I’m afraid I’m at a loss for suggestions. It sounds like Reader Extensions may not be configured properly for your form since it’s not enabling “local save” on the PDF (such that Reader is able to save the form).

As for gotoURL() and importData(), you should be accessing these as “xfa.host.gotoURL()” and “xfa.host.importData()” — could that be the problem?

How about ordering for the form-ready event?

What I’m after is a field in the form that is the last one to execute the form-ready event.