This is not just a Net Worth report problem. I have experienced the
same problem with other reports and have "come up" with the same "fix/work
around". I have found that a report that acts up on one day does not
necessarily act up on another. Past states of computer cycles seem to make
a difference.
--
Kent Riesen
Eureka, CA


"James R" <j_reins[at]charter.net> wrote in message
news:ylZDh.24$bD3.15[at]newsfe03.lga...
I have noticed that one of my net worth over time favorite reports refuses
to load. If I watch the CPU, it appears that $ is in an infinite loop with
the load bouncing back and forth between 50 and 80%.

But the really amusing thing is this: during the loop if I select "custom
date", change either the start or stop date (move either to a new date, or
just touch one - change a date and move it back) and select the APPLY
button, the load will converge. If you select the OK button, the load will
not converge.

I have saved a net worth report that converges and attempted to reload it
via the Favorites option, and it loops. I have performed quick and standard
database repairs with no resolution. However, I suspect that there is some
problem in my database/budget since I have other, more simple reports that
do not loop. But... what's REALLY interesting is that there seems to be a
software path within $ that's stable (APPLY), and one that is not (OK).

I have noticed that one of my net worth over time favorite reports refuses
to load. If I watch the CPU, it appears that $ is in an infinite loop with
the load bouncing back and forth between 50 and 80%.

But the really amusing thing is this: during the loop if I select "custom
date", change either the start or stop date (move either to a new date, or
just touch one - change a date and move it back) and select the APPLY
button, the load will converge. If you select the OK button, the load will
not converge.

I have saved a net worth report that converges and attempted to reload it
via the Favorites option, and it loops. I have performed quick and standard
database repairs with no resolution. However, I suspect that there is some
problem in my database/budget since I have other, more simple reports that
do not loop. But... what's REALLY interesting is that there seems to be a
software path within $ that's stable (APPLY), and one that is not (OK).