|
From: Dieter S. <dsi...@sq...> - 2001-11-05 23:46:14
|
You could use sequence too. I increment the number in the code so I can create different combinations to form a string for the invoice number. Dieter Simader http://www.sql-ledger.org (780) 472-8161 DWS Systems Inc. Accounting Software Fax: 478-5281 =========== On a clear disk you can seek forever =========== On Mon, 5 Nov 2001, Qaexl wrote: > Hey there, > > I'm in the middle of creating a couple modules for this client. One > of them is a Point-of-Sales module that's a mishmash of the ct.pl and > is.pl modules. More like a "wizard" to make it easier for the POS > staff. (I'll upload it somewhere if anyone's interested, once I'm > done). Going through there, though, I noticed that the invoice number > doesn't use a sequence, but rather a chunk of Perl code that > determines the last known invoice number, then increments it from > there. > > While this client won't have more than one POS terminal any time soon, > I am concerned about this if there ever were. The liklihood of two > people creating duplicate invoice number is slim to none -- but, I'd > like to hear the developer's opinion on this. It is my understanding > that the COMMIT command insures that there's no possibility of this > happening. Wouldn't it be safer to use a sequence instead? > > |