MS Access data conversion - Autonumbering failure after conversion from 2.0 to 2003

Author

Autonumbering failure after conversion from 2.0 to 2003

knud.n@mail.dk

2005-12-19, 8:26 pm

Hello Everyone

After converting my database from 2.0 to 2003 format, using the
converter downloaded from microsofts homepage, all the fields that uses
autonumbering does not work. Instedet of generating a correct
incrementet number, the autonumbering generates a large negative
number.
Does anyone have any suggestions ???
Any help is very much appreciated, thanks.

Douglas J. Steele

2005-12-19, 8:26 pm

Why do you say that's not a correct number? Unless you're using a
Replication ID Autonumber, the Autonumber is simply a Long Integer, which
means that any value between -2,147,483,648 to 2,147,483,647 is legitimate.

Autonumbers exist for one purpose only: to provide a (practically
guaranteed) unique value that can be used as a primary
key. -21,641,464, -21,641,463, 21,641,461 (or -21,641,464, 18, -3,632)
serves that purpose just as well as 1, 2, 4.

Fact of the matter is, Autonumbers are seldom displayed to the user anyhow,
so it shouldn't make any difference. If the value of the number matters to
you, you probably shouldn't be using an Autonumber.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

<knud.n@mail.dk> wrote in message
news:1135021927.799100.31450@z14g2000cwz.googlegroups.com...
> Hello Everyone
>
> After converting my database from 2.0 to 2003 format, using the
> converter downloaded from microsofts homepage, all the fields that uses
> autonumbering does not work. Instedet of generating a correct
> incrementet number, the autonumbering generates a large negative
> number.
> Does anyone have any suggestions ???
> Any help is very much appreciated, thanks.
>

2005-12-19, 8:26 pm

Autonumbering has never worked exactly right in Jet 4.0.
They added the ability to reset the Autonumber, and ever
since have been fixing bugs where the Autonumber reset
to the wrong value. Each bug they fix seems to create or
expose a new one. (And with the eminent release of Access
12, there is no reason to expect Jet 4.0 will ever work
correctly)

Here is Allen Brownes code to fix this common failure:

Fixing AutoNumbers when Access assigns negatives or duplicates
http://allenbrowne.com/ser-40.html

(david)

<knud.n@mail.dk> wrote in message
news:1135021927.799100.31450@z14g2000cwz.googlegroups.com...
> Hello Everyone
>
> After converting my database from 2.0 to 2003 format, using the
> converter downloaded from microsofts homepage, all the fields that uses
> autonumbering does not work. Instedet of generating a correct
> incrementet number, the autonumbering generates a large negative
> number.
> Does anyone have any suggestions ???
> Any help is very much appreciated, thanks.
>

Sponsored Links