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]> > 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 > > ______________________________**_________________ > 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
