Please Explain the effect on online accounts in the new-release copy function
Jay Gourley
Member ✭✭✭
In Quicken for Windows, does the new-release copy function disconnect all online accounts? It appears to be doing that on data file. If I make a copy now, the online accounts in the copy are no longer online accounts. The accounts remain set up for online syncing in the original. This is new in the latest release or next to latest release. In previous versions the copies kept the online synch information with the copy.
0
Answers
-
If you haven't already, you may want to review the release notes: https://www.quicken.com/support/update-and-patch-20182019-release-quicken-windows-subscription-product
A more detailed explanation is provided in the help document: https://help.quicken.com/pages/viewpage.action?pageId=178919681 -
Hello @Jay Gourley,
Thank you for reaching out to the Community with your question.
Yes, the new file copy process does disconnect all online accounts and will require you to (re-)establish online connections.
The reason for this is to improve troubleshooting and resolution for issues related to data file damage as well as online/internal server issues. This process works the same as though you would be creating a brand new data file and establishing online account connections for the first time rather than "repairing" existing connections that may be damaged in the original file.
I hope this helps!-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
Thanks, Sherlock and Anja. Your replies answer my immediate question. But now I have follow-up. It used to be true that the best practice ensure data file integrity was to use Quicken to make a record-by-record copy of the data file and then validate that copy. What is the best practice now that that is no longer practical? I don't want to wait until corruption becomes so bad that I notice the problem and then have to go far back in time for a restorable backup.0
-
Jay Gourley said:Thanks, Sherlock and Anja. Your replies answer my immediate question. But now I have follow-up. It used to be true that the best practice ensure data file integrity was to use Quicken to make a record-by-record copy of the data file and then validate that copy. What is the best practice now that that is no longer practical? I don't want to wait until corruption becomes so bad that I notice the problem and then have to go far back in time for a restorable backup.0
This discussion has been closed.