On Wed, 3 Nov 2010 21:51:39 -0000, "Ron Ferguson" <[email protected]> wrote:
>It doesn't actually work like that. > >Consider that you use the Legacy defaults, then instead of having it just in >the Data folder the path would be C:\Legacy\Data\DropBox\fergy.fdb, on a >second machine it might be stored in My Documents with the path being C:\~My >Documents\Legacy\Data\DropBox\fergy.fdb. I am not concerned about where the fdb is stored. That should not be a problem with Dropbox (as you stated) ... other than my concerns about live updates that I expressed at the end of my previous post (and the end of this one). If you re-read my post, I was trying to illustrate my concerns about PATHS TO MULTIMEDIA LINKS that are stored in said fdb. Just like the case when Dropbox is not involved ... if you copy a database to another machine the file structure for the multimedia files must be the same or you will have to fix things (maybe an easy fix, or maybe not). And I was also trying to point out that not all "C:\My Documents" folders are created equal. >On changing the fdb file in the first computer, the file is copied to the >DropBox server in the sky, and on opening Legacy on the second PC it will >copy the file to that DropBox, overwriting the contents. Which concerns me because we are talking about an Access database with tables and rows getting updated right and left all the time. My database is 48mb. If I change a tag on an individual does it upload 48mb to the Dropbox server? Then if I untag, does it upload another 48mb? Even on a high-speed connection (where upload speeds are usually 1/10th the speed of downloads) this can take a lot of time. Maybe this is described in the Dropbox documentation, which I haven't read. It just seems like the potential traffic associated with placing a database in a Dropbox folder would be problematic. I personally would be leery of this configuration. It may work OK 99% of the time. But does it work 100% of the time? And when it doesn't, how will you know it didn't? I have a Dropbox account and it works great for certain things. For example, I think it works great as a way to backup your database (i.e. tell Legacy to write the backup zip's to the Dropbox folder). But I don't think I would trust it with the task of keeping two WORKING copies of a database in sync. To each his own I guess. -- Dennis Kowallek (LTools) http://zippersoftware.com/ltools http://groups.yahoo.com/group/ltools 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
