Paolo Benvenuto <[EMAIL PROTECTED]> writes:
> > Well, unless you only have those three transactions, it will guess from
> > other transactions around it.
>
> but in that transaction the exchange rate does not have an ambiguity error:
> the exchange rate is well defined!!! :
Maybe -- the code doesn't know how to handle a 3-commodity
transaction. Where I've seen this problem is where you have a normal,
two-split transaction between accounts A and B, but the commodity of
account A is different from the commodity of account B, and BOTH are
different than the "transaction currency".
Yes, the exchange rate is easily determined between A->B, but the code
does not currently deal with it.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
