OK, here

It could easily be done, but recommending such a solution to human visible fields would be:

Of the old man as he was taking his siesta-

It was the stinging kind, a most egregious pest, a

Vicious thing-the bear got mad. "I'll fix it good!"

The stout fly catcher said. "And this is how I'll do it!"

With that, he grabbed a boulder with his forepaws, stood

On his hind legs and, using all his strength, he threw it,

Straight downward, managing in the event to smush

The fly and, with good aim and rotten logic, crush

His poor friend's skull and lay him out in rigor mortis.

...from La Fontaine's fabel "The Bear and the Gardener"

Found here: http://www.lafontaine.net/lesFables/fableEtr.php?id=422

These days does it even make sence to use portals and relationships for containerfields, since the portal can be cut into smaller chunks scattered over the layout. The lesson is repeaters have only it's use for utility purposes!!!

--sd

Write a script to loop through the repetions. If repeatfield[1] = "" then Set Field repeatfield[1] = value Else If repeatfield[2] = "" then Set Field repeatfield[2] = value Else, etc.

See attached sample file. Note that the repeating field must be on the current layout, with all repetitions displayed and a consecutive tab order defined.

SetNextEmptyRep.zip

-Queue- So, the next field is really the next repetition? I didn't realize that! Is the key having a consecutive tab order for the repetitions? I suppose so.

Yes. As long as the tab order is consecutive throughout the repetitions, Go to Next Field is equivalent to 'Go to Next Repetition'.

Thanks for the info guys!

I realized that was an option (transpower's suggestion) early on in trying to solve this problem, but tried to avoid going that route because of the number of reps. Instead, I've decided to put all my values in a seperate table and create a relationship to it. More flexability that way. Thanks again.

I've got another question about email integration that I'll ask in a seperate post.

Instead, I've decided to put all my values in a seperate table and create a relationship to it. More flexability that way.

Which is the way to ...usually!!! You might even be able to trace OS2 or CP/M fanatics somewhere as well

--sd