Do you have to ID the field for autotab to work?

Question

I have a form with text fields I'm using to caputre dates of service. It has the following fields
Month1, Day1, Year1, ToMonth1, ToDay1, ToYear1. They are each set to a max char value of 2.
I would like the PDF to AutoTab to the next field when the current one has reached its max.
I found the following code:
// Document-level function
function tab_next(next_field_name) {
    // Move to next field if Enter key is pressed
    // or the user has clicked outside of the field
    // or if the number of character is the character limit
    if (event.willCommit || AFMergeChange(event).length === event.target.charLimit) {
        getField(next_field_name).setFocus();
Then call it like this as the Keystroke script of a text field:
// Autotab to the "Day1" field
tab_next("Day1");
This code works, but I need to add a keystroke script to every text field. And in the example, I have Month1, Day 1, Year1... well, the actual form goes up to Month11, Day11, and Year11.
Coding each field with a custom script, naming the next field to auto tab to.... this seems tedious. Is there a way to modify the code, so rather than defining what field to autotab to next, it should look at the tab order, and go to the next one without having to specifiy it specifically.
Is there a way to code it, so it autotabs to the field next on the tab list? Or must the field it autotabs to be specifically identified in each instance of the script.
Thanks very much in advance.

Answer 1

No. Part of the problem is the tab order is dynamic since it depends on the read-only and display state (hidden or not) of the fields, which can change at any time via scripting.
You could come up with a field naming convention that could help, making it possible to determine the next field name based on the name of the field that called the script. Or you can set up an object or implement a linked list to specify the custom order, and the script could look up the next field based on the current field, but it might be simpler to just hard code the field names.