Trevor Best <nospam@localhost> wrote in
news:4128b7fd$0$11205$afc38c87@auth.uk.news.easyne t.net:
[color=blue]
> The way I do for multiple warehouse receipt numbers is
> WarehouseNo/Increment, if you must have only one series of numbers
> you could pool them, IOW when satellite connects to main to
> replicate you also then look at the number pool and take say if
> you expect 10 transactions before next replication take 15 numbers
> minus the number of numbers you had left over from last
> replication.[/color]
The easier way to do this in a replicated database is to use a
compound key, one column indicating the replica, and the second the
unique ID in that replica's data set.
Of course, if you really need a human-readable number in sequence,
you're going to have to pre-allocate ranges of numbers to each
replica, as you say.
From my point of view, jet replication has simply been made obsolete
by the ease of use and cheapness of implementing Windows Terminal
Server. The only scenario I can think of where that won't work is
something like laptop users who have to work disconnected in the
field and then connect to the home base to synch. Replication is
still viable there, but I don't see much need for something like
invoice numbers in that scenario, since the folks in the field are
not going to be responsible for billing (work order numbers or
quotation numbers or something like that could easily be uniquely
keyed to the replica or to the user who created them).
--
David W. Fenton
http://www.bway.net/~dfenton
dfenton at bway dot net
http://www.bway.net/~dfassoc 
