ACCESS FEED: [MS_AccessPros] RE: auto number ID in table

Rabu, 23 Oktober 2013

[MS_AccessPros] RE: auto number ID in table

Daniel

The order of the records is not really important. If you primary key is the main index it will probably be how the rows are ordered. It could be that you sorted the table at some time that used another field. You can always sort again on the PK if it's important to you.

Some of the tables I build are just left alone as to how they sort, but then there are others I want to sort on another field just for my own viewing. Things like user group permissions usually get a separate field that I name SortOrder. I use that field to sort things like combo boxes when I want things like user groups in a specific order that is not based on alpha. When I use them I always leave substantial gaps like 10, 20, ...100 just so I can fit any new groups in between existing ones.

---In ms_access_professionals@yahoogroups.com, <daniel2478a@yahoo.ca> wrote:

Hi All,

my database is split in to front and back end, my primary ID is an auto number

I can delete records but wont get them back, (or that ID), thats ok

I noticed that when I do compact and repair then I end up with some errors, not sure how those occur?

after that I notice that my ID is not in order anymore

1, 2, 3, 4, 5, 6, 7, 8, 9...

turn into

6, 7, 8, 1, 2, 3, 4, 5, 9...

what can cause this?

also is it safe to add and rename columns later to a database? (not changing data types)

thanks,