Auto Number Problem (very Strange)

[sdimaggio]

I have an interesting problem and wonder if anyone has seen this happen.

I have a table with a "Date" field. And have it sorted by date. I then inserted an "auto Number" column. When I completed the task about 15 records were out of sync. Those 15 records should have been on the record numbers 22,000-22,014. Instead, they appeared on record numbers 9-23.

Why did Access do this and How do I fix the problem?

Steve.

Ps. There are no primary keys in the table when I do this.

 

[MichaelRed]

Hmmmmmmmmmmmmmmmmmm.


How much of relational database are you familiar with?


A rationale underlying relational databases is the concept of abstraction. You the programmer are not suposed to be concerned with the physical details of the data. Records may be added/deleted/modified without your involvement in the record placement. Likewise, the use of an "AutoNumber" or similar identity field (GUID) is not intended to keep a sequence of values acording to the order of entry of records in a db, but to just provide a record identifier, generally to use as a 'relational' KEY for other tables.

The db "engine" is, in general, free to insert records anywhere within a "table", and to present the records in any order -unless the recordset is oredered by ...

Many dbs routinely 're-use' the space made available by the deletion of records and some dbs actually perform an add/delete transaction sequence for an edit operation, thus the 'physical' order of the records can become rather 'hapahzzard' fairly quickly.


MichaelRed
m.red@att.net

There is never time to do it right but there is always time to do it over