Problem

In Goldenseal estimating software versions 4.6 and earlier, you can end up with an Assembly that still uses an old component price, if you change a component, then alter the price of that component before saving the change in the Assembly.

This problem happens because the Cost Item change happens before a link is established between the Assembly and the new component, so the Cost Item doesn't know it is included in that unsaved Assembly.

Caught By

Turtlesoft testing

Workaround

If you change components in an Assembly, hit the Enter key to save the changes, before changing the prices of any new components.

Solution

Starting with Goldenseal 4.7, we do some extra checking before posting from material price changes, and update properly even if an Assembly is currently in a partly revised state.

NOTE-- This might seem like an extremely rare condition, but in fact users are probably more likely to notice and change a price, right when they enter it into an Assembly. Our trainer noticed it at one of the estimating training classes.

Technical Details

Programmer note-- code changed in CCostItemViewer::IsReadyToUpdateObject