I realize the nature of a global field is temporary or session-based, but I've seen some uses that I can't replicate.

Is there a [non-scripted] way to preserve the values of a multi-repetition global field such that the field is not cleared when the file is opened?

Asking because Brian Dunning's Chartmaker app does something along these lines, but I don't see how any script is refilling or bypassing the field in question.

... take the file off the server. Then set the globals values -- in a single user environment, all changes to globals are preserved.

Global calculations can also work well. I don't know how they would work with the repetitions - I guess if the iterations can be calculated values or if the global calc references a standard rep field or another global. Method Genx suggests is probably what is being used here ... I'm unfamiliar with ChartMaker.

I never could really get global calc's to work properly, though it's most likely that i could never see a reason to rely on them...

Globals, by their very nature, are stored (including global calcs). But we are talking about fairly static data here where unstoredness (is that a word?) is unnecessary. This value will populate on every User station when they open.

most likely that i could never see a reason to rely on them

I agree, we're dealing with a structural problem here!

--sd