Re: Reports Not Responding Windows 10

2018-01-23 Thread Christopher Lam
Your account currency is R. Your report currency is $. Your data file has no R/$ price information. That's why. Edit option, change report to R. On 23 Jan 2018 16:52, "michaelwithms" wrote: I have installed Gnucash this morning. All fine except the reports do not carry

Re: Reports Not Responding Windows 10

2018-01-23 Thread Maf. King
On Tuesday, 23 January 2018 04:24:07 GMT michaelwithms wrote: > I have installed Gnucash this morning. All fine except the reports do not > carry totals across . i am win10 user . please see screen shot > > Hi Michael, My

Re: Reports Not Responding Windows 10

2017-12-22 Thread David T. via gnucash-user
I had to check on my own machine (Mac OS X 10.11.6 GC 2.6.14), but there are no delays here. I had to check because, for me, the first report is always run at startup, when I am not really paying attention. If the problem really is a delay on the first-run report only, perhaps a workaround

Re: Reports Not Responding Windows 10

2017-12-22 Thread John Ralls
The 30 seconds delay special Windows is in addition to the time necessary to compute a report from a large book. With the 20+ years of history in my primary account it can take 3 or 4 minutes to generate a report. That part runs the progress bar so that one at least sees that something is

Re: Reports Not Responding Windows 10

2017-12-22 Thread David Carlson
John did not elaborate. This is worst in Windoze. It is still slow in Linux, but much less so. This will eventually improve but there is so much work under the hood needed to get there that it may not be noticeably improved even in the 2.8 series of releases If you have a big data file, slow

RE: Reports Not Responding Windows 10

2017-12-22 Thread Ken Pyzik
TiBo TJ -- I have Windows 10 and while I see a similar behavior -- I have found that you need to be patient and the report will eventually show up. Try and wait for up to about 30 seconds. I know it's a long time -- but it eventually does show up. This is a known bug that has been presented in