There are several known bugs that cause JET 4 databases (Access 2000, 2002,
and 2003) to generate duplicate autonumbers.
A bad one was fixed in SP7 for JET 4, so you might like to check that you
have SP8. Info:
http://support.microsoft.com/kb/239114
Another issue is discussed in:
http://support.microsoft.com/?id=884185
but the problem is more generic than the kb recognises. Essentially,
executing any append query that specifies the value for the autonumber and
appends data to a linked table is likely to cause the problem.
Another issue includes a failed write that typically occurs if you have a
main form and a subform both bound to the same table.
Importing/converting from an older Access database can also set the Seed
badly.
More info and workarounds in this article:
Fixing AutoNumbers when Access assigns negatives or duplicates
at:
http://allenbrowne.com/ser-40.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"flogyu" <(E-Mail Removed)> wrote in message
news:EF5F55D0-C57B-4995-9E97-(E-Mail Removed)...
> Hello,
> have anyone ever met autonumber field duplication?
> Phenomenon: an app. running genarally error-free, sometimes collapses due
> to
> value duplication in autonumber field because seed value
> fails(decreasing).
> As for I am the author, for sure, there are no any VBA code dealing with
> seed
> value adjusting( at least Intentionally). Might it be an error in Jet
> engine,
> or a tricky bug in my program, that leads to such an error like this?
> Environment: Acc 2002, Jet 4.0.
> The app runs over WindowsServer 2003, Terminal services.
> Your help would be appreciated.
> Flogyu