I'll need to put an example together for you I expect, but I'm sure I've had the problem where I have dropped new children in under a parent, and hierachical calc's don't auto-execute.
Yes, I'm aware of this, but this is not related to auto-update. Auto-update is date related only. Other calculations should update when a parameter is changed. However, as you noted, there is still cases where this is not done (and a manual recalc, or a Touch, is required)
[quote=Pierre_Admin] Auto-update is date related only. [/quote]
Yes... I know.
My idea was just to have my equations "relatively" current to avoid mistakes -- at least, when I'd wake up in the morning, IQ would've done it's midnight thing and fields would be reflecting the real totals, mins, maxes, etc.
This is far from ideal, but I'm just thinking of some intermediary solutions....
[quote=Pierre_Admin]
Other calculations should update when a parameter is changed. However, as you noted, there is still cases where this is not done (and a manual recalc, or a Touch, is required)
[/quote]
Are they not updated because of some "bug" or is this by design ?
[quote=Pierre_Admin]
True. Currently, Touch will calculate up the hierarchy. Recalc will only look at the immediate children. There are reasons for this, but I'm not claiming that they are good ones...
[/quote]
I think it would help to know the reasons.
Like : I'd like to know why Recalc doesn't recalculate from the bottom up (or top down when necessary), and just forget the "touch" feature.
(side note : I'm always using the forum in "flat list" mode, not threaded... I'm just having too much trouble following a threaded thread... This explains why I'm often -- probably -- not answering to the right post. Sorry about that.)
Yes, I understand that, but often hierarchies equations are not updated "properly" in my dB, and that makes them frighteningly unreliable.
Could be because:
1- changes are (mistakenly or not) made to an item higher in the hierarchy, not taking into account children's value for instance 2- an item with values that should affect a parent's total is just *moved* under that parent (that has no effect on hierarchical calculation for some reasons, which can really mess things up). 3- all subitems Value are just deleted and all parent's total stay the same (when hierarc.equ. is set to MIN for example with date fields)... [EDIT : this also happens when an item is completely deleted -- just experienced it with a MAX hierarchical equation : I deleted the subitem which had the max value, and parent didn't update]. 4- F9 doesn't work properly of you're not at the right level of the hierarchy to recalculate (if there's a mistake in a hierarchical calcultation it won't recalculate the full hierarchy, but only the direct children, which means that you have to already need to be aware of where the problem lies... which might be impossible if numbers or equations or more or less complex)
Could be because of other reasons... I'm not sure what else could affect/disrupt hierarchical calculations -- haven't tested that thoroughly (but you maybe could could you tell me/us ?)
In any case, when things like that happen, it can become a mess and I have to go into field management and manually reapply the equation. Yes, it's slow (the process of opening the window, etc. + IQ's own calculations)... but I don't know any other way.
=======
There's also another thing I sometimes find challenging to have to cope with : there's no way of determining whether a value has been calculated or directly entered by me (the user). It would often simplify things to know that fact (am I the conscious source of the discrepancy, or is my equation flawed, or is there something wrong elsewhere, etc.).
True. Currently, Touch will calculate up the hierarchy. Recalc will only look at the immediate children. There are reasons for this, but I'm not claiming that they are good ones...
Comments
Auto-update is date related only.
[/quote]
Yes, I understand that, but often hierarchies equations are not updated "properly" in my dB, and that makes them frighteningly unreliable.
Could be because:
1- changes are (mistakenly or not) made to an item higher in the hierarchy, not taking into account children's value for instance
2- an item with values that should affect a parent's total is just *moved* under that parent (that has no effect on hierarchical calculation for some reasons, which can really mess things up).
3- all subitems Value are just deleted and all parent's total stay the same (when hierarc.equ. is set to MIN for example with date fields)... [EDIT : this also happens when an item is completely deleted -- just experienced it with a MAX hierarchical equation : I deleted the subitem which had the max value, and parent didn't update].
4- F9 doesn't work properly of you're not at the right level of the hierarchy to recalculate (if there's a mistake in a hierarchical calcultation it won't recalculate the full hierarchy, but only the direct children, which means that you have to already need to be aware of where the problem lies... which might be impossible if numbers or equations or more or less complex)
Could be because of other reasons... I'm not sure what else could affect/disrupt hierarchical calculations -- haven't tested that thoroughly (but you maybe could could you tell me/us ?)
In any case, when things like that happen, it can become a mess and I have to go into field management and manually reapply the equation. Yes, it's slow (the process of opening the window, etc. + IQ's own calculations)... but I don't know any other way.