Re: Manually entering historic records

2018-01-15 Thread Liz
On Tue, 16 Jan 2018 15:03:04 +1000 Dave H wrote: > I use Dropbox however I maintain my gnucash data file on my local > drive rather than directly in Dropbox. I think from memory the lock > file hangs around in Dropbox so when you try to re-open your data > file the LCK file

Re: Manually entering historic records

2018-01-15 Thread Dave H
I use Dropbox however I maintain my gnucash data file on my local drive rather than directly in Dropbox. I think from memory the lock file hangs around in Dropbox so when you try to re-open your data file the LCK file is still the and triggers the warning dialog. As others have said you can just

Re: Manually entering historic records

2018-01-15 Thread David Carlson
Trevor, Have you tried making a copy of the file on your local drive and working on it there. I have never worked with dropbox so I have no idea if it could confused by the way GnuCash makes backups, for example. David C On Mon, Jan 15, 2018 at 9:39 PM, Chris Smith wrote:

Re: Manually entering historic records

2018-01-15 Thread Adrien Monteleone
I’d choose “Open Anyway” as well, but you could also delete that LCK file. That’s the one causing the problem. (Note, it is supposed to be there if you have the file already open, but since you know for a fact you don’t, you can delete it. Normally, this file is deleted when you close the

Re: Manually entering historic records

2018-01-15 Thread Chris Smith
If you don't have it open elsewhere you can click "Open anyway" Depending on how it shutdown the lock file may be there. On Jan 15, 2018 9:31 PM, "Trevor Richards via gnucash-user" < gnucash-user@gnucash.org> wrote: I'm not making much progress... I see I got some replies to my manual entry

Re: Manually entering historic records

2018-01-14 Thread Colin Law
On 14 January 2018 at 09:59, Gregory L. Davis wrote: > Trevor: > > It sounds to me like you have to increase the number of days for "Read only" > transactions. Try clicking on the file menu, then preferences. In the > "Accounts" tab, increase "Day Threshold for Read-Only

Re: Manually entering historic records

2018-01-14 Thread Gregory L. Davis
Trevor: It sounds to me like you have to increase the number of days for "Read only" transactions. Try clicking on the file menu, then preferences. In the "Accounts" tab, increase "Day Threshold for Read-Only Transactions (red line):". You can set the number of days to to something like

Re: Manually entering historic records

2018-01-14 Thread Rick Copple
Hi Trevor, What exactly is it doing to prevent you from entering past dates? I enter them all the time. You do have to enter the / dividers. Like instead of 11418 you would have to enter 1/14/18 to get the date to come out right.  -- Rick Copple On Jan 14, 2018, at 12:15 AM, Trevor Richards

Manually entering historic records

2018-01-13 Thread Trevor Richards via gnucash-user
I've been following the user group for years but still not started the move from 20yrs of MSmoney... all looks too hard with an MSM file with records back to 1997. I thought I could test the water with a new business and associated bank account that started in 2016.I've been managing this with