You misunderstood Paul

I'm not changing a date, I'm changing an order number, specifically oe.ordnumber, it's just that I use a date sequence when I create order numbers for some clients. I'm not mucking with any dates or numbers or anything to do with accounting ledgers, I just want the order number changed so it locates itself in the proper place when I print a report. due to the typo it sits at the bottom of the list. It's just that once an order is closed there is no way to re-open it and change the ordernumber so if you created it with a typo and didn't notice it until after the invoice has been printed the only way to correct the typo is by editing the table directly.

Jeff Roberts
J.R. Electronics
604-241-1362


On 11/24/2011 11:11 AM, Paul Tammes wrote:
The field you want to change is just a date, but it just might be the accounts have been closed for the year (period) in which the order was raised. I suggest to play with the preference settings of the user printing the order, change that from dd/mm/yy to yy/dd/mm might do the trick.
Then print, and no hacking of data or database is needed.

Bad workflow and ethics by the way. IRS and the likes will frown if you change data from previous periods, but that is another matter.

Hth
Paul

2011/11/24 Jeff Roberts <[email protected] <mailto:[email protected]>>

    Hi all

    I did an upgrade earlier this year, upgraded to PGSQL 8.4 on
    FreeBSD and SQL-Ledger 2.8.32.

    Now when I look at the database with PGAdmin III it says that
    public.oe doesn't have a primary key or OIDs and that I can view
    it but not edit it.

    I want to change the order number of a closed order so that a
    listing comes out in the correct form, (the order number was
    entered day/month/year/# instead of year/day/month/#)

    How is SQL-Ledger entering and editing this table without a
    primary key or OIDs?

    What do I need to be able to edit my tables again?

-- Jeff Roberts
    J.R. Electronics
    604-241-1362 <tel:604-241-1362>

    _______________________________________________
    SQL-Ledger mailing list
    [email protected] <mailto:[email protected]>
    http://lists.ledger123.com/mailman/listinfo/sql-ledger



_______________________________________________
SQL-Ledger mailing list
[email protected]
http://lists.ledger123.com/mailman/listinfo/sql-ledger
_______________________________________________
SQL-Ledger mailing list
[email protected]
http://lists.ledger123.com/mailman/listinfo/sql-ledger

Reply via email to