Autonumbr field gone crazy!

  • Thread starter Thread starter Simon
  • Start date Start date
S

Simon

Hi,

I created a database in Access 98 around 18months ago.
About 2 months ago I converted it across to Access 2000 - no
problem................... until last week.

Now, when I try to create a new record in the form - or the table - I get an
index/duplicate error.

I have just run a test not and have noticed the following:-

1/ Autonumber Record Numbers run from 0 - 4316

2/ When I add a new record, Access tried to give it record Number
3807 which, of course, is already used.

3/ RecNo is the only primary Key in the Table.

Has anyone else come across this crazy behaviour or advise me what is
happening and what to do?

Many thanks in anticipation.

Simon
 
Have you tried a repair and compact? That would be the first thing to
try. Look under "Tools" - "Database Utilities"
 
Hi,

I created a database in Access 98 around 18months ago.
Click to expand...

Access 97 I presume? there was no Access98... but no matter.
About 2 months ago I converted it across to Access 2000 - no
problem................... until last week.

Now, when I try to create a new record in the form - or the table - I get an
index/duplicate error.

I have just run a test not and have noticed the following:-

1/ Autonumber Record Numbers run from 0 - 4316
Click to expand...

It's a known bug in Access2000. Microsoft says that installing the
latest JET Service Packs should fix it, but I've seen indications in
these forums that this may not be absolutely true. See

http://support.microsoft.com/?id=257408
 
Simon, you can try my idea, but you should go with Wayne and John. I
have not been following 2000 problems
 
Installing the service pack is supposed to prevent the problem from
developing, but does not fix the tables that already have their Seed set
wrongly.

After installing the service pack, run the code in this link to reset the
Seed.
http://allenbrowne.com/ser-40.html
If your database is split, run the code on the back end.
 
Installing the service pack is supposed to prevent the problem from
developing, but does not fix the tables that already have their Seed set
wrongly.

After installing the service pack, run the code in this link to reset the
Seed.
http://allenbrowne.com/ser-40.html
If your database is split, run the code on the back end.
Click to expand...

Thanks Allen - I knew I'd seen this but couldn't remember whose code
it was! Bookmarked.
 
Back
Top