FrontAccounting forum — Purchase order primary key not in synch with PO #

Re: Purchase order primary key not in synch with PO #

null@example.com (apmuthu) — Wed, 31 Dec 2014 12:39:54 +0000

Thanks Janusz. That was fast!

Re: Purchase order primary key not in synch with PO #

null@example.com (itronics) — Wed, 31 Dec 2014 11:58:43 +0000

This should be considered as small bug. The reference should be moved back if the last PO is cancelled, I will fix it in table branch repo in a while. Thanks for pointing it out.

Janusz

Purchase order primary key not in synch with PO #

null@example.com (apmuthu) — Wed, 31 Dec 2014 08:25:45 +0000

* Delete a Purchase Order, (#2)
* Create a new one in it's place.
* Tested with the last one in the table (auto_increment)
* The New PO now takes this vacated value (#2) but the screen view shows the header line as PO #3 (the auto_incremented table id value) whilst the reference shows 2 and the printout (pdf) also shows it as PO 2.

This has potential for confusion but is probably left there to track the primary key of the actual record in the database.

@joe: any light?