Had fixed? Sounds like it might be broken again, or like some user installed a non fixed version?
To add to the consternation: I am using the "community version" which calls itself SQL-Ledger 2.8.33 (not Ledger123) on the version screen. Installed using git, so it should be fixed, I take it? 2011/7/24 Sebastian Weitmann <[email protected]> > On 24/07/11 18:26, Armaghan Saqib wrote: > >> Hi Jean, >> >> I am not 100% sure but I do think I had fixed this issue in one of my >> bank reconciliation updates. >> >> Are you using Ledger123 (available from github) or SQL-Ledger >> (available from sql-ledger.com)? >> >> Regards >> Armaghan >> > > Hi Armaghan, > > You are right. Yes, you did correct this in L123 some time last year. I > remember having this problem and your solving it. > > Regards, > Sebastian > > > > ______________________________**_________________ > SQL-Ledger mailing list > [email protected] > http://lists.ledger123.com/**mailman/listinfo/sql-ledger<http://lists.ledger123.com/mailman/listinfo/sql-ledger> >
_______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
