autonumber behavior

[john]

I have an Access 2000 application. One central database
with two users linked to the Access 2000 data. One table
has an Autonumber field set to Long Integer, Increment. It
seems that every so often, the next increment instead of
taking the next available higher number, will take a
number somewhere in the middle (had been deleted). For
example, if the next increment should be 1000, the
autonumber will take 486 (one that had been deleted
earlier at some time). This behavior is not consistant and
may only happen with a users accessing both halfs of the
application (forms and data) over the network. Is this a
known bug?

Thanks

 

[Tim Ferguson]

Is this a known bug?

It was with early versions of Access 2000, and was meant to have been fixed
with SP1, although there have been reports here of anomalous behaviour with
autonumbers even with the service pack.

First aid, in any case, would be to check your version level and bring it
up to date with the latest SP and Jet updates.

HTH


Tim F

 

[Guest]

I have run into the same problem, and I updated to Jet SP8
(the latest) but the problem is still there. This is
reported in KBase Article ID 257408.

 

[Hedi]

For article ID 257408, it will still repro if you use ADO
(even if you upgrade to the latest Jet) so to get around
it I update my recordset in the code using DAO for this
special case.
If you don't update thru code using ADO, updating to a
later version of Jet will fix the problem.