S
simcon
has anyone come across this problem in Access2003
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A
Allen Browne
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
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
S
simcon
Allen - No the autonumber is not being seeded intentionally.
Is there a known bug in Access 2003
Is there a known bug in Access 2003
S
simcon
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:"
problem regarding auto number duplication or negatives
"These steps will reproduce the problem in Access 2000, 2002, or 2003, with
all service packs applied:"
A
Allen Browne
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.
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.
S
simcon
thank you Allen the article on your website was most helpful