tag:infinitekind.tenderapp.com,2009-01-14:/discussions/iphone-ipod-touch-ipad-android-app-questions/12411-sync-with-upgrade-from-201710-1706-to-20191-1855Infinite Kind: Discussion 2019-05-26T18:10:23Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/469845572019-02-20T19:04:46Z2019-02-20T19:04:46ZSync With Upgrade from 2017.10 (1706) to 2019,1 (1855)<div><p>I plan to upgrade from 2017.10 (1706) to 2019,1 (1855). I am running on two Windows 7 machines using the Dropbox Folder sync method. Things are running perfectly with the current configuration.</p>
<p>For previous upgrades with 2017, I simply installed the new version on both computers and everything was fine on both computers and the sync system. Is there anything different required for the 2019 upgrade with sync? I just want to be aware of any potential procedure changes before I dive in.</p>
<p>Thanks.</p>
<p>James</p></div>jamesyeltag:infinitekind.tenderapp.com,2009-01-14:Comment/469845572019-02-20T20:40:22Z2019-02-20T20:40:22ZSync With Upgrade from 2017.10 (1706) to 2019,1 (1855)<div><p>I'm a fellow user.</p>
<p>TIK have never posted a guide on upgrading when syncing is being used.</p>
<p>For myself I would take the following approach.</p>
<ol>
<li>
<p>Ensure all machines have synced all transactions between them so that all are up-to-date</p>
</li>
<li>
<p>Take a local backup of Moneydance data on each machine.</p>
</li>
<li>
<p>Shutdown Moneydance on all machines</p>
</li>
<li>
<p>Start Moneydance on the primary machine and upgrade it. Look through the data and ensure that all looks correct</p>
</li>
<li>
<p>After the upgrade shutdown Moneydance on the primary machine.</p>
</li>
<li>
<p>Start Moneydance on the secondary machine and upgrade it, look through the data and make sure it looks OK</p>
</li>
<li>
<p>Shutdown Moneydance on the secondary system</p>
</li>
<li>
<p>Start Moneydance on Primary machine and start using it. Enter some transactions</p>
</li>
<li>
<p>Start Moneydance on secondary machine. check to make sure transactions are coming over. Enter some transactions</p>
</li>
<li>
<p>Go back to primary machine and make sure transactions are replicating.</p>
</li>
</ol>
<p>My aim is to not have any transactions replication while there is a version mismatch between systems and to make the upgrade very procedural with checks as you go along.</p></div>dwgtag:infinitekind.tenderapp.com,2009-01-14:Comment/469845572019-02-20T21:36:36Z2019-02-20T21:36:36ZSync With Upgrade from 2017.10 (1706) to 2019,1 (1855)<div><p>Thanks dwg. That is basically my procedure when doing an upgrade. Hopefully, no special steps are required for 2017 to 2019. I'll certainly give it a shot.</p>
<p>James</p></div>jamesyeltag:infinitekind.tenderapp.com,2009-01-14:Comment/469845572019-02-24T18:06:31Z2019-02-24T18:06:31ZSync With Upgrade from 2017.10 (1706) to 2019,1 (1855)<div><p>dwg,</p>
<p>Thanks again for your upgrade suggestion. I had a little time delay getting getting the upgrade done, but 2019.1 is now syncing nicely between the two Windows 7 computers. No installation issues.</p>
<p>I will let that settle in for a while and then see about adding an Android device to the mix.</p>
<p>James</p></div>jamesyel