I have a db with a number of tables that have autonumber primary keys. In
one of the tables, the autonumber is suddenly incrementing incorrectly. The
last number added was 291 and it's now trying to add number 245 (instead of
292).

By the way, that data tables are all in a back-end mdb, with the programs,
forms, reports, queries, etc. in a front-end mdb.

Compact and repair did not help. I was able to correct the problem by
creating a new mdb and then importing all the tables from the old mdb into
the new one.

Anyone know why this happens?? Also, more importantly, is there a better
way to correct the problem??

> Anyone know why this happens??

Dodgy version of Jet files on one of your workstations. Make sure ALL
workstations have the latest (SR8+) version of Jet. Download Jet from
MS, or apply all Windows security releases to Win XP.

> Also, more importantly, is there a better way to correct the problem??

? better ?

You can run code like this:

members.iinet.net.au/~allenbrowne/ser-40.html


(david)


"JP" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have a db with a number of tables that have autonumber primary keys. In
> one of the tables, the autonumber is suddenly incrementing incorrectly.
> The
> last number added was 291 and it's now trying to add number 245 (instead
> of
> 292).
>
> By the way, that data tables are all in a back-end mdb, with the programs,
> forms, reports, queries, etc. in a front-end mdb.
>
> Compact and repair did not help. I was able to correct the problem by
> creating a new mdb and then importing all the tables from the old mdb into
> the new one.
>
> Anyone know why this happens?? Also, more importantly, is there a better
> way to correct the problem??
>
>