Re: Changing tax.pm in 1.21 for a new tax which replaces two old taxes

[Luke <..hidden..>]

Clearer might be an expired flag, along the lines of an inventory 
obsolete.  I do like the idea here, though.

I was trying to come up with a "tax replaces tax" mechanism that would not 
have the same problems as Gerald's solution and then some, but could not 
in the limited time i chose to think about it.

Luke

On Mon, 5 Jul 2010, Chris Travers wrote:

> Currently what I'm doing for my customers is to set the rate to 0
> effective when the tax is no longer collected, and to remove it from
> the drop down once no more invoices could be generated (usually at
> next book close).
>
> One change that might be desirable might be to exclude 0-rate taxes
> from retrieval.  This would also avoid db changes during a production
> branch, and would seem to my mind to be closer to expected behavior.
> Any feedback?
>
> Best Wishes,
> Chris Travers
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Ledger-smb-devel mailing list
> ..hidden..
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel