well, running totals are not my specialty...DBlank seems to get them, but here are 2 ways off the top of my head to get what you are after.

1) create a section below the running total (I am guessing that it is in Details...so a Details B) just to be sure that the running total has been incremented.
Create a formula like:
shared numbervar maxBal;
if {@runningTotal} > maxBal then
maxBal := @runningTotal;

I would probably try suppressing the new section, the formula should still work, then in the GF2 you would put a formula like:
shared numbervar maxBal;

and just to complete the trilogy, in the GH2 you would have a formula like:
shared numbervar maxBal:=0;
""//will hide the 0 on the report.

the other way would be to basically use the same values as above, but calculate the running total yourself...
so the only 'big' difference would be that you don't need the running total or the extra section. The formulas would look like:
gh2: shared numbervar maxBal:=0;
shared numbervar rt:=0;
""

detail:
shared numbervar maxBal;
shared numbervar rt;
rt := rt + {table.field};
if rt< maxBal then maxBal:= rt;
""

gf2:
shared numbervar rt;
and another formula
shared numbervar maxBal;

some ideas, hopefully one of the works for you.

Glad to hear it.

Brief explanation:
GH2: this resets the variable
DetailB: this checks after every line to see if the value of the running total is greater than the variable, if it is, store the new value in the variable
GF2: Display the value.

If CR didn't have running totals or don't quite understand them (like me) then you can use a similar method to build your own running totals (which is how I do running totals)

Hope this helps and lets you add one more tool to the kit