How to share data across multiple machines

[Bob Brush]

If you have a consistent connection to the internet the lock file will sync so fast that it won't usually be a problem, keep an eye on the bottom left corner when gnucash starts, it will show the modification time, a helpful thing if you want to make sure you are using the most recent version.
The easiest way to cause a Dropbox problem is to disconnect from the internet then start gnucash, the remote location could then start gnucash not knowing, and assuming that Dropbox being synced everything is good.  Gnucash is well behaved, one problem that happens from time to time is leaving work with gnucash open, because autosave is set, you would expect it to overwrite the file every so often.  At home you are warned by the lock file, but select open anyway, and would expect a Dropbox battle, but the autosave is smart, it only writes if there are changes, so it can really just sit there all weekend, no damage :)  The safe thing to do when you find Gnucash open like this when you return to work is to reopen, checking that it's the latest version.

Bob


> On Jan 31, 2014, at 6:43 AM, Jonathan Kamens <jik at kamens.us> wrote:
> 
>> On 01/31/2014 04:18 AM, Colin Law wrote:
>> Opening twice on the same file is not a problem as the lock will ensure (unless you override it) that one of them is read only. Using dropbox there is no such lock so it is easy to open it on both machines, modify and save.
> Why won't there be a lock when Dropbox is used? As far as I can tell, the lock is just a file that GnuCash creates in the filesystem in the same directory as the data file when it starts up, so when it creates that file, shouldn't Dropbox automatically sync it to the other machine(s)?
> 
>  jik
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.