From: <la...@cl...> - 2008-05-21 18:03:53
|
No response as of yet on this one... Looked further into the issue, it seems during the database upgrade the qty type had went from real to double precision. It seems weired that the value had went from 10.83 to 10.8299999237061 and not 10.8300000000000 (probably during some alter table modify column command) as the original value was entered as 10.83. I can probably use some more time to look into this, but for now I have updated the io.pl to format qty like sellprice. $form->format_amount(\%myconfig, $form->{"qty_$i"}, $decimalplaces, $zero) This issue impact only existing invoice (I hope) and I can now get old invoices to print only the two decimal place. Any input on if this is gonna break anything would be great. For now, I can only rerun the yearend reports using the old and new systems an hoping that their bottom lines match. It would be annoying for them to be off by $0.01. Thanks ahead for any comments! Tim > hello...we are testing our upgrade from 2.4.11 to 2.8.14 and the default > precison is set to 2. Everything seems fine but the qty. for an example > invoice went from 10.83 to 10.8299999237061. My guess is that the > precision doesn't apply to qty. anyone knows how i can fix this? This line > item was shipping so for most of the time it isn't an integer. Sending a > customer an invoice with this many decimal place seems confusing...thanks > ahead for your help...regards, tim > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users > |