GoogleDrive works the same way as Dropbox, in that a file is stored on each computer you have connected, which then synchronizes to the file on GoogleDrive. If the file is open on more than one device at the same time, a conflict version is created.
I'm not certain the timing of the sync ... I thought with Dropbox it happened only after the file was closed, but with GoogleDrive it seems to be happening when the file is open. This makes no sense, as changes in the file are occurring while the file is being synched, causing these conflict errors and causing Legacy to have all sorts of issues. Something seems really wacky here, and my guess is its with GoogleDrive. I can experiment by moving my data file back to Dropbox, else I may need to contact GoogleDrive. I'm curious with people here if you are currently using GoogleDrive and are seeing an issue. Trying to isolate which application is causing the issue! FYI, I am on GoogleDrive 1.17.7290.4094 Scott On Mon, Oct 13, 2014 at 9:03 PM, Richard Young <[email protected]> wrote: > I used to keep my Legacy files on GoogleDrive but went back to Dropbox. I > found GoogleDrive too slow in syncing. I will load my test database on > GoogleDrive and see if I have any problems. > > Richard > > > On Mon, Oct 13, 2014 at 8:56 AM, Scott Hall <[email protected]> wrote: > >> I've started to have conflict errors with my file stored on GoogleDrive. >> I just started noticing this today. >> >> Does anyone else use GoogleDrive to store their data files? I had used >> Dropbox with no problems, but needed more space, which is cheaper on >> GoogleDrive. >> >> It seems that whenever GoogleDrive is synching the file, it creates a >> conflict -- even when the file is OPEN. It should not synch open files. >> >> Any thoughts? >> >> Scott >> >> >> Legacy User Group guidelines: >> http://www.LegacyFamilyTree.com/Etiquette.asp >> Archived messages after Nov. 21 2009: >> http://www.mail-archive.com/[email protected]/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/[email protected]/ >> Online technical support: http://www.LegacyFamilyTree.com/Help.asp >> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and >> on our blog (http://news.LegacyFamilyTree.com). >> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp >> > > > > -- > Richard Young > 480.220.7391 > [email protected] > www.familyhistorytech.com > @fhtek > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
