Autonumbering/merging problem

[Paul Hyett]

I have a names & addresses database set up with an auto-numbering
reference field at the beginning. (Access 2002)

Today I tried to merge in same new records from a CSV text file, and it
wouldn't accept them as they 'didn't have a non-unique reference in the
first field'.

I then edited the text file, giving the records reference numbers
directly following the last auto-numbered ones, and tried merging again.

This *appeared* to work, but when I went in to add new records
afterwards, the autonumber for the new record came up as something
absurd, like 5E07 (there are only about 800 records in the database).

Any ideas what went wrong?

 

[mattia]

I have a names & addresses database set up with an auto-numbering reference
field at the beginning. (Access 2002)

Today I tried to merge in same new records from a CSV text file, and it
wouldn't accept them as they 'didn't have a non-unique reference in the
first field'.

I then edited the text file, giving the records reference numbers directly
following the last auto-numbered ones, and tried merging again.

This *appeared* to work, but when I went in to add new records afterwards,
the autonumber for the new record came up as something absurd, like 5E07
(there are only about 800 records in the database).

Any ideas what went wrong?

 

[Paul Hyett]

"Paul Hyett" <[email protected]> ha scritto nel messaggio

Hi, you seemed to reply to my post, but I saw nothing new appended to
what I wrote?

 

[Paul Hyett]

I have a names & addresses database set up with an auto-numbering
reference field at the beginning. (Access 2002)

Today I tried to merge in same new records from a CSV text file, and it
wouldn't accept them as they 'didn't have a non-unique reference in the
first field'.

I then edited the text file, giving the records reference numbers
directly following the last auto-numbered ones, and tried merging again.

This *appeared* to work, but when I went in to add new records
afterwards, the autonumber for the new record came up as something
absurd, like 5E07 (there are only about 800 records in the database).

Any ideas what went wrong?

So I guess this must be an unknown bug, then?