After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 105331 - report generators should complain if they don't find exchange rates
report generators should complain if they don't find exchange rates
Status: VERIFIED DUPLICATE of bug 340991
Product: GnuCash
Classification: Other
Component: Reports
1.8.x
Other Linux
: Normal enhancement
: ---
Assigned To: Chris Lyttle
Chris Lyttle
Depends on:
Blocks:
 
 
Reported: 2003-02-05 20:12 UTC by Tomas Pospisek
Modified: 2018-06-29 20:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tomas Pospisek 2003-02-05 20:12:02 UTC 
Instead of showing you a report that is completely zeroed out, when 
you've got a different default report currency than the currency of the 
account(s) the reportgenerator should complain and tell you: 
 
"Please set your default currency to XXX or define an exhange rate" 
 
or 
 
"Some accounts are empty because your default currency is different from 
the currency of some of the accounts. Please change your default currency 
or define exchange rates from those currencies into your default report 
currency". 
 
And thanks for GnuCash (happily using gnucash for 3 years now :-)!
Comment 1 John Darrington 2003-10-22 03:18:35 UTC 
It's worse than this.

If there are some accounts in the default currency, but others in
another currency, then the others are ignored by the report generator
EVEN IF there are prices in the price database to convert between them.

The only way to get the report generator to consider all the accounts
is to ensure that there are transactions between them, which cannot
always be assumed.
Comment 2 Christian Stimming 2006-05-23 11:06:47 UTC 

*** This bug has been marked as a duplicate of 340991 ***
Comment 3 John Ralls 2018-06-29 20:27:31 UTC 
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=105331. Please update any external references or bookmarks.