primary key collisions due to auto reseeding of auto number field.

  • Thread starter Thread starter simcon
  • Start date Start date
Can you be more specific, Simon?

Is the AutoNumber being seeded intentionally?

Or is it one of the causes listed at the top of this article:
Fixing AutoNumbers when Access assigns negatives or duplicates
at:
http://allenbrowne.com/ser-40.html
 
Allen - No the autonumber is not being seeded intentionally.
Is there a known bug in Access 2003
 
Allen would we be better developing in Access 2007 in order to resolve this
problem regarding auto number duplication or negatives

"These steps will reproduce the problem in Access 2000, 2002, or 2003, with
all service packs applied:"
 
Simon, I would expect Access 2007 to have the same problems.

2007 also had additional problems with AutoNumbers, but MS addressed the new
problems in SP1 (released this week.) I haven't retested these under A2007
SP1, but I have no reason to expect they would be fixed.
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

MS Access problem 0
Auto email when due date is due 2
The next Grand Theft Auto title has been officially announced 0
To restart from 1 primary key auto incriment column MSAccess 20 2
Primary Keys yes or no? 8
Auto Generate Primary Field Value 5
change numeric value in primary key 2
Data Entry Form and Auto Number ID 2

Back
Top