Report comment

Good points Jeremy.
I had observed the fact that I would be locked-in to using a predetermined variable as my iterator, but don't often find myself having to nest my for loops.

In most instances I can think of where I'd need to do that, I'm able to take advantage of a built-in FileMaker construct to do it instead (example:
Loop/
GoToRecord[ExitWhenLast]/
EndLoop)

Since it seems so infrequent that I need a nested for loop, and because moving this code into a custom function gives the benefits of both enhanced readability, and enforcing consistency of iterator names, I think I'm going to stick to this technique for the time being, and reevaluate next time I need a nested for loop.

Thanks for the link though, I'm new to filemakerstandards.org, and hadn't seen that discussion on there yet.