AutoNumber in Access 2010 breaks

MS Access split application (.mde, .mdb)
300 sites
5 year history
Includes a table which has a field which is the Primary key and is AutoNumber data type.
Just 3 sites running on MS Access 2010.  All using .mdb vs .accdb file format.
One site only is experiencing dysfunction of the AutoNumber field. Ie. It does not try to use the next available value. It tries to use a previously used value causing error of ‘duplicate value in index’.
We have reset the value AutoNumber attempts to use successfully. Unfortunately, the problem recurs after a week or so of use.
Is this a known problem with MS Access 2010? I do not find this as reported problem.
slgoetzeAsked:
Who is Participating?
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Connect With a Mentor Database ArchitectCommented:
Can you please Accept an answer and close the question ...

thx.mx
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
"We have reset the value AutoNumber attempts to use successfully. "
How are you doing the reset?

"Is this a known problem with MS Access 2010"
Not that I have heard of.

Can I assume you have done a Compact & Repair on the db ?

mx
0
 
slgoetzeAuthor Commented:
Thanks for the response.
What we do to reset:
1. remove relationships
2. ALTER TABLE Activity ALTER COLUMN SeqNo COUNTER(somevalue,1);
3. add back relationships
4. compact and repair
The above is successful and the db is ok for a week or two then breaks again.
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
I have no definitive answer per se.
My suggestion is ... Import all objects (just tables I assume in BE) into a new blank mdb... and try that.

Seems this db has some sort of corruption going on in this particular mdb.

mx
0
 
slgoetzeAuthor Commented:
Thanks. Must be something ugly in it. Unfortunately, it will appear fixed then 'break' again in a week or two.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
The Import of BE into a new container should be quick to try .... ?

mx
0
 
slgoetzeAuthor Commented:
Unfortunately, it will appear fixed then 'break' again in a week or two.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Have you already tried this ?

If not ... it could easily fix the issue.  db Containers do become corrupt.

mx
0
 
slgoetzeAuthor Commented:
No mx, we have not performed this.
Do you have a link of steps. Have not done this in a long time.
Relationships, Table Definition and Data, right?
0
 
GRayLCommented:
Listen to him.  Create a new database.  Make it the current database.  Click File, Get External Data, and import all the Objects from the old database into the new database.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Create a blank MDB, then pretty much the steps below ....

mx
Capture1.gif
Capture2.gif
Capture3.gif
0
 
slgoetzeAuthor Commented:
Thanks mx.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Good luck.  Report back on results please.

mx
0
 
slgoetzeAuthor Commented:
We will get the .mdb from the site and try.
0
 
slgoetzeAuthor Commented:
May be a few days...
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Has this question been resolved?  Can we close the question ?

thx.mx
0
 
slgoetzeAuthor Commented:
yes
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.