q_lurker said: a) Is it worthwhile reducing the number of transactions in the account (will it have any major effect on the file stability, reliability, performance etc.). IMO, for spending accounts, No. I don't think number of transactions has any impact on any of those behaviors. For investment account, I have found in older versions of Quicken slower responsiveness as number of transactions exceeded some gray line (dependent on other software, hardware, OS, and user expectation). I have three spending accounts wit over 5000 transactions in each. No issues. I have been using one data file for all record-keeping since 1991.b) Does the Quicken file size reduce if a large number of transactions are deleted from the account ?The file size only reduces if you follow up that deletion with a File / File Operations / Copy operation.
NotACPA said: @eqpu Your "Size of QDF file" is 1/3rd the size of my file. Even with your upcoming "few thousand transactions" you'll still be approx 1/2 my file size.SO, I wouldn't worry about it.And, file size has no identified impact upon Q's performance. If you're having performance issues let us know and there are other things to try. BUT in letting us know, we'll need to know the specific actions that you believe are involved.
Rocket J Squirrel said: You may have the Quicken preference "Automatically memorize new payees" enabled. I find this to be overkill, memorizing everything. I keep my list trimmed to 13 months just so I don't lose any annual payees.After any mass deletion, do File > File Operations > Copy as @q_lurker mentioned above. Only this copy operation lifts the data records and drops them into new tables, leaving behind items marked as deleted.
Rocket J Squirrel said: You may have the Quicken preference "Automatically memorize new payees" enabled. I find this to be overkill, memorizing everything. I keep my list trimmed to 13 months just so I don't lose any annual payees.