[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Locking Last Cost

On Tue, Sep 29, 2009 at 7:52 PM, Joseph <..hidden..> wrote:
I've jumped from SQL-Ledger 2.2.7 to 2.6.27 in hope that I would be able to use most stable version 1.2.9 but uploading the sql-ledger database to ledgersmb
is not the way to go I think as I got a lot of error messages and could no longer long in into ledgersmb.

So, I deleted the database and reloaded a new one.
I've notice that Ledgersmb does not change the last cost in the database upon ordering or changing the exchange rate, that is good.

How to do upgrade?

The upgrade scripts are in /sql/legacy/ in the LedgerSMB directory.

Before you begin:  select version from defaults;

Then start with that version (Pg-upgrade-2.6.14-2.6.18.sql for example) and run each script in sequence until you run out of them.  This will bring it up to speed.  If a script errors out, ask for help here on this list.

Best Wishes,
Chris Travers


On 09/29/09 18:54, Chris Travers wrote:
>On Tue, Sep 29, 2009 at 5:10 PM, Joseph <..hidden..> wrote:
>> Is there a way to prevent Last Cost from changing when receiving an order;
>> or lock it down?
>> When I recorder a PO the cost is changing to average cost, I think.
>And the average cost function in the app is mostly useless at the moment
>too.  I expect to have this corrected for 1.3 as well.
>However, if you want to, you can replace the lastcost() and avgcost()
>functions in the db with ones that return this field from the parts
>Best Wishes,
>Chris Travers
>> --
>> Joseph


Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
Ledger-smb-users mailing list