autonumber error

[spring]

We have a table with an autonumber field which now ranges from 1 to 10000,
somehow the autonumber jumped back to 7000. therefore new records cannot be
added because of key violation.

I temporarily solved this problem by inserting 3000 new records and then
delete.

(above numbers are just for easy explanation)

It happened twice and i want to know how could it happen or how to prevent?

Thanks in advance!

 

[Larry Linson]

If I recall correctly, there was an autonumber error in one of the earlier
versions of Access. I think that was Access 2000 and I think it was resolved
by one of the Service Packs to that release. Search the Microsoft Knowledge
Base for "autonumber error" and see if you can find that. Or, just make
certain that you have all the Service Packs installed for the version of
Access you are using.

Larry Linson
Microsoft Office Access MVP

 

[David W. Fenton]

If I recall correctly, there was an autonumber error in one of the
earlier versions of Access. I think that was Access 2000 and I
think it was resolved by one of the Service Packs to that release.

Jet 4, because it introduced the capability to programatically
control the Autonumber seed value, had many bugs in the early
versions. It was not until Service Pack 6 that Autonumbers were
safe, if I'm remembering correctly. That, combined with Access SR1a
or later.

 

[spring]

David,

in my case, it's access 2003 in XP SP3
the jet 4 engine was already the latest when the problem occured.
(4.0.9511.0 for Msjet40.dll ).

Thanks all the same!