Does auto-increment work reliably in Access 2010?

In Access 2003 and 2007 auto-incremnt numbers can become corrupted.  See http://allenbrowne.com/ser-40.html and
http://support.microsoft.com/?id=884185

Can anyone tell me whether this has been fixed in Access 2010?   Is there an authoritative document, preferably from Microsoft, that tells whether this has been fixed?

Thanks!
anAppBuilderAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
This is *EXTREMELY* rare ... and *not* something I would worry about.

mx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cyberkiwiCommented:
If you take the first link as authoritative (since you posted it), read this in there

You may be able to solve the problem with a compact/repair:
    * In Access 2010:  Compact and Repair Database on the Database Tools ribbon.

What does that tell you?
The problem with the conditions of the issue like "linked tables" is that Access is not in total control.  As with any database system, it may crash and corrupt in any version.
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Auto Numbers are a fact of life in Access database design, and have for the most part .... 99.99999999 % been extremely reliable since Access 1.0.

I would have zero fear of using Auto Numbers.

mx
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
If your really that concerned with it failing, then you should use a key generation routine and assign your own key.  But as MX has said, this is extremely rare.  I cannot think of an instance yet were I've failed to get a proper key and I've been using Access since ver 1.1.
Heck, just look at the number of conditions from that MSKB article that you need in order to see it fail.
JimD.
0
dportasCommented:
Apparently this is a problem with JET / ACE databases. If it's a problem to you then you could always use Access with SQL Server Express or some other DBMS instead. There are of course plenty of other more significant benefits to using another more powerful DBMS.
0
Armen Stein - Microsoft Access MVP since 2006PresidentCommented:
Although most of the Access applications we build for clients use a SQL Server back-end these days, when we do use an Access back-end we always use AutoNumber primary keys.  Over hundreds of systems since Access 2.0 we have never had a problem with them corrupting or duplicating.
0
anAppBuilderAuthor Commented:
thank you all
0
anAppBuilderAuthor Commented:
Thank you!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.