I have a database that has been replicated, with two users entering data on
local replicas and synchronising with the parent dbase on a server. The
Autonumber function in several tables has started jumping around, not
assigning consecutive numbers for new entries. One edit of existing data has
caused the Autonumber entry for that record to *change* to a large negative
number. I'm okay with Autonumber being completely random, but I was under
the impression that the numbers were issued consecutively (randomness will
change how I organize some searches...)

Does this sound like "normal" behavior for a replicated database? If not,
any suggestions? I have tried compacting the database but these oddities
persist.

thanks -
ElizCat

Yes, that's normal for replicated databases, and you cannot change it. The
idea is to ensure that you can add records in multiple databases, so using
random autonumbers minimizes the risk of two databases using the same value.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"ElizCat" <(E-Mail Removed)> wrote in message
news:1271C668-EB9B-4596-A9BD-(E-Mail Removed)...
> I have a database that has been replicated, with two users entering data
on
> local replicas and synchronising with the parent dbase on a server. The
> Autonumber function in several tables has started jumping around, not
> assigning consecutive numbers for new entries. One edit of existing data
has
> caused the Autonumber entry for that record to *change* to a large
negative
> number. I'm okay with Autonumber being completely random, but I was under
> the impression that the numbers were issued consecutively (randomness will
> change how I organize some searches...)
>
> Does this sound like "normal" behavior for a replicated database? If not,
> any suggestions? I have tried compacting the database but these oddities
> persist.
>
> thanks -
> ElizCat

Thanks Doug. I suspected that was the case, but the negative numbers really
threw me for a loop.

"Douglas J Steele" wrote:

> Yes, that's normal for replicated databases, and you cannot change it. The
> idea is to ensure that you can add records in multiple databases, so using
> random autonumbers minimizes the risk of two databases using the same value.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>