autonumber messes up with me.undo

Similar Threads:

1.AutoNumber, messed up sequence, duplicate values.

Hello,

I have a database that is used by about 20+ users entering about 1000 
records per day. I am noticing that they are having trouble adding records to 
the DB sometimes. When they have trouble, I go into the database table and 
try to add a record manually at the source and sometimes it tells me that the 
Autonumber is creating a duplicate record. As I scrolled through the data in 
the table I noticed the following....

Autonumber type field called "RecordID"

1-1085   looks good

then it jumps to 3741 through 3749

then it jumps to 16864 through 17074

I know some people are hitting the Undo button to back out records that are 
half way done because they changed their minds about creating those records. 
Other people start a record, get about half way and leave the record like 
that for about 30 minutes. Would starting a record and not completing it 
cause problems for everyone else? Btw I am sharing this db over a possible 
inconsistent 1GB WAN connection.


Do you know what is causing the Autonumber to jump around and cause 
duplicates?

Your help is greatly apreciated.


Iram

2.Autonumber mess, figure out the number

I am in autonumber hell, it is important for me to get the AutoNumber
even in case of previous deleted records, and I cant get the value
through a 'test' insert and then delete method.  There is no VBA
function that has that value in memory somewhere.  That would be the
ideal.

For example:

AutoNumber-Field:
1
2
3
4
5 *-
6 *---- I need to delete these records
7 *-
8 *
9 * 

*Delete*
so now I have

1
2
3
4
 --> Next insert
10

From the example above, I really need to get that value '10' without
performing a 'test' insert,  I was thinking of using a meta-table or
something, other than that I think I have tried everything, any ideas?

3.Messing with autonumber

I recovered an old Access database for new use. I simplified it removing 
unwanted tables. I uaed get external data.
Unfortunately I forgot to set the primary key "ID" to autonumber and I left 
it as "number". Now I have to enter manually a progressive number.
I tried to generate another primary key (with the proper autonumber 
specification).
With both primary key the database works (but I still have to enetr manually 
the proghrssive numbers in the original primary key.
If I delete the old primary key, I end up loosing my preexisting one_to_many 
relationship.
Help!!
-- 
Sergio Biguzzi

4.Autonumber mess

Hi All,

I have a database that is experiencing problems with 2 tables. There's
an AuditMaster table and an AuditResults table, with a one to many
relationship.

The Key for AuditMaster is AuditID which is an autonumber.

It was index with no duplicates allowed but this has come off
somewhere down the line.

There are now duplicate AuditID's...

The only way I can see to fix this problem is to have the Autonumber
start from 2500, where it is currently at 900~.

Is it possible to have the autonumber commence from 2500 now?


Thank you

Adam

5.autonumber and undo

If a user starts a new record and then realizes the record already exists or 
gets interrupted or whatever and clicks on an "Undo" button (me.undo) or 
click the "exit without saving" button (DoCmd.Close acForm, 
"frmSelectCustomer", acSaveNo), the record is not saved but the next new 
record entered is no longer sequential in the autonumber field.

Why is this? Not a big deal, mainly curiosity (I use DMax for required 
sequential fields).

6. AUTONUMBER Field Increments after "UNDO / CLEAR FORM"

7. Undo list: figuring out how many times to undo

8. Undo feature for MS Word - what "exactly" will it "undo"