Extend the "Set Password to modify transactions..." function to include downloaded transactions

Tom Young

The "Set Password to modify transactions…" function currently only responds to user-entered changes to historical transactions. Changes to historical information that are associated with "downloading", e.g. changes to Opening Balances, should be scrutinized in the same fashion, even in Accounts with "Automatic Entry is: On."

Similar to the doctor's Hippocratic oath of "primum non nocere," (first, do no harm) a financial program that at it's heart is an accounting program should have a similar promise of "don't screw with accepted historical data."

Jim_Harman

Another instance where this would have been useful was a couple of years ago when Quicken messed with historical paycheck entries.

This would act as a backup to catch cases where a Quicken bug causes it to try to change historical data.

Chris_QPW

Easy to say, impossible to implement at this stage.

Jim_Harman

At least they could find the code that changes the opening balance and add a warning popup, with an option to prevent the change.