Does GnuCash possess a Journal Entry numbering facility

[Michael Hendry]

On 9 Oct 2014, at 17:27, Buddha Buck <blaisepascal at gmail.com> wrote:
> 
> On Thu, Oct 9, 2014 at 12:19 PM, Derek Atkins <warlord at mit.edu> wrote:
> Michael Hendry <hendry.michael at gmail.com> writes:
> 
> > It’s essential, though, for _every_ transaction to have a unique (and
> > human-friendly!) number for this method to work.
> 
> I'll just point out that currently the former is true -- each
> transaction *does* have a unique number.  The issue is "human friendly".
> Currently it's literally a random 128-bit number (a GUID).  So there is
> no order.  One *could* use just a portion of it, like a 32-bit section,
> as your number.
> 
> Well, random 122-bit number; 6 of the 128 bits are fixed. For my purposes, I tend to find the first few bytes to be sufficient to find a particular guid in a list.
> 
> But this ID is not exposed to the user, and this discussion seems to assume that a sequential ID is useful.
> 

I, for one, find that a sequential ID is sufficiently useful to justify the extra effort involved in my work-around.

Being a fallible human, I occasionally put the same number in twice, or forget I’ve switched between registers and press the “+” key to increment the number field - which will increment the last number entered for _that_ register, and cause an overlap.

Michael