How to protect data from being changed when upgraded

baddabing

"Set pw when modifying transactions" …… Does this prevent changes to the data when upgraded for the whole database or just the file.?

Quicken Anja

Hello @baddabing,

Thanks for reaching out!

The “Set password when modifying transactions” setting is specific to each Quicken data file. That means if you have it enabled in one data file, it won’t automatically apply to another data file you open.

If by “upgraded” you mean installing a new Quicken update/release, this setting should remain applied in that data file, and shouldn't be affected by updating Quicken.

If you mean upgrading your subscription (for example, from Deluxe to Premier), the setting should also remain applied in the data file where you set it. Upgrading your subscription should not change or remove this setting within that data file.

So in short: it’s data-file specific, and normal updates or subscription upgrades should not remove it.

Hope this helps!

NotACPA

@baddabing

BUT NOTE that there's a long standing bug in Q, the precise cause of which hasn't yet been determined, that if you change download methods into an account (say, Direct Connect to Express Web Connect or any other change) OR if you "RESET" an account that you download, the "Opening Balance" in that account might inadvertently get changed.

Which is why it's recommended that for any downloaded banking (not investment) accounts, you save the correct Opening Balance in the Memo field of that transaction also.

That way, if there's a problem with reconciling the account, you can take a quick look at the OB transaction and see if it got changed AND know what the correct amount should be.

Boatnmaniac

https://community.quicken.com/discussion/7972323/how-to-protect-data-from-being-changed-when-upgraded

With QWin the database and the file are one in the same…there is no difference.

When you set a PW to protect transactions, you also need to enter a date. The PW protection then applies to all transactions prior to and including that date. Transactions dated after that date are not protected.

Having transactions PW protection set up will require you to enter a PW every time you wish to edit any transaction in the protected date range.

From time-to-time you can update the protection-thru-date.

This setting is intended to prevent you from accidentally entering changes to older transactions that you do not want changed without serious consideration.

I have no idea if it would protect those transactions from a Quicken Classic/QMobile/QWeb data sync issue or version update issue that might occur from time to time. You could try setting it up and then monitor it to see if it provides you with more data integrity/stability for older transactions.

I think I might try setting it up myself because sometimes when changing connection methods the Opening Balance transaction dollar amount gets changed. I think it would be good to know if this setting will prevent that from happening in the future.

Jim_Harman

I have a "Set password to modify transactions" password enabled and in the past that has NOT prevented Quicken from changing my Opening Balance.

However the Release Notes for R66.11 say that Quicken now adds an adjustment transaction at a more recent date when reconnecting accounts rather than changing the Opening Balance. We'll see what impact that has.

Boatnmaniac

https://community.quicken.com/discussion/comment/20545262#Comment_20545262

Well, that's too bad but I've now got the PW protect set in all 4 of my primary data files. Good thing I also have the correct Opening Balance transaction dollar amounts entered into the Memo fields of those transactions so I'm covered.

baddabing

Thanks