[AccessD] Office 365 update issue ?

[Paul Hartland]

Hope its not the same problem I had a few years back, was on an old version
of Access can't remember which, but suddenly new records wouldn't insert
because of a duplicate number, the field was an autonumber & primary key,
like you a compact & repair failed to resolve the issue and it had me for
hours (maybe days thinking about it) until I found an article something
like in a certain situation if a record is deleted that has an autonumber
field the autonumber may lose its sequence, for example you have 5 records
with the autonumber running 1,2,3,4,5  record 3 is deleted, then for some
reason the next record is given the autonumber of 3 and no problem since 3
was deleted but then the next record inserted tries to assign 4, 4 is
already there...bang duplicate....In the end the only solution I could come
up with was resetting the autonumber & relinking all related tables etc
right pain.

Paul

On Tue, 3 Dec 2019, 02:09 Mark Simms via AccessD, <
accessd at databaseadvisors.com> wrote:

> VBA code that was working for over 4 years suddenly threw an error last
> week.It was basically adding a new record into a table whose primary key is
> ID (autonumber).A duplicate key error message is being thrown (3022).Has
> anyone encountered this problem ? A compact and repair on the back-end
> database did not resolve the issue.I have confirmed with the client that
> they are subscribed to Office 365.
>
> Mark Simms
> marksimms at verizon.net
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>