Issues encountered after restoring a Backup
Found at:
"Recently, a couple of accounts in my Quicken file became corrupted. I asked a few questions to the community trying to avoid using a restore action, but eventually, I had to hit the restore button. I picked the latest backup file that I was certain did not include the corrupted records. The file was a month earlier. Once the restore function completed I found the following issues: ...."
[I question whether the original poster was able to accurately determine whether the restored file contained any applicable corruption - before using that restored file. Some of the "issues" reported by the op, once he began using the restored file, could be related to data corruption.]The op goes on to list four "issues" found in the restored file, the first three of which are not "issues" at all, just user lack of understanding.
The original poster assumed that it was necessary to deactivate, then re-activate, the 20 problem accounts ... one account at a time. Definitely NOT true.
The simple approach is to deactivate all the problem accounts one at a time.
Then initiate the Add Account process (from the Account List or the Account Bar) for the financial institution(s)/user-id(s) that were deactivated ... one financial institution/user-id at a time.
When the Add Account process successfully logs on to the financial institution and "discovers" the accounts held there for the provided user-id, it will send that information to Quicken. Quicken will in turn present the user with a dialog box containing a "list" of ALL the discovered accounts with the option to Add, Link, or Ignore each Found account.
Rinse and Repeat for each combination of financial institution/user-id.
In that manner ALL accounts for the same financial institution with the same user-id can be "re-activated" at one time. The original poster made much more work out of the process than necessary.
While exactly what is happening in the op's issue number four is not clear (due to poor problem description), the op seems to be saying that now transfers entered in one Quicken account and intended for a different Quicken account are (apparently) filling-in the FROM account (in square brackets ) in the Category field of the transfer transaction (creating what is sometimes known as a "transfer back into the same account" or a "self-transfer" in Quicken report Customize dialogs). Typically, when the Category field is filled in by Quicken, the filled-in information is taken by Quicken from a Memorized Payee (that process is known as "QuickFill").
That may not be what the op wants, but his comment regarding that in "Note 2" saying "This issue should be identified as a bug in Quicken. Under what scenario, [can?] a person transfer money within the same account?" clearly shows a user who has rushed to make public pronouncements without knowing what he is talking abount. As noted by me just above, such transfers are definitely a part of Quicken (every Quicken generated account "opening balance" transaction, is such a transaction ... every Quicken generated account opening balance transaction is "a transfer back into the same account".
Since I did not attempt to locate the discussion(s) about the op's original "corruption" problem, I can't offer anything there.
But as to the op's current issue #4; unexpected Quicken QuickFill results involving incorrect data in the Memorized Payee List (if that is the cause of issue #4) have been reported fairly frequently; and they seem to be usually (always?) caused by Syncing to the Cloud. Since it is a trivial matter to turn off Sync and test doing a download or two with Sync OFF, that should be one of the first steps tried. And lest anyone be inclined to jump to another conclusion: I think it's likely that even if having Sync OFF prevents screwing up the Memorized Payee List for the future, that will most likely NOT fix any screwed up memorized payees ... the user will probably have fix any memorized payees manually.
[NOTE: see also the first post in the discussion by Sherlock.]