Question: Purpose of table Indexes and quantity per table

[Ruegen]

trying to fully understand indexes in a table

Under a field's General properties in a table there is Indexed then I have it as default as Yes (No Duplicates)



recently I got an error when adding a field saying there was too many indexes for the table and I had to change the new field to no

Just to wrap my mind around this one, why would I want to index the field, is there much point to it? Am I increasing the performance, why is there a limit etc

[ranman256]

Only need for an index field,no dupes, is for parent/ child relations, and LARGE lists...(millions)
if you don't have either of these, access will still find the data. The db will still function fine.

[Ruegen]

Only need for an index field,no dupes, is for parent/ child relations, and LARGE lists...(millions)
if you don't have either of these, access will still find the data. The db will still function fine.

Thanks - that is pretty much what I thought too

[CJ_London]

this link will tell you about indexes

https://support.office.com/en-US/Art...a-38c6c4f1a0ce

and this link tells you about the limits in Access of a whole variety of things

https://support.office.com/en-za/art...9-ea9dff1fa854

Of relevance to you

Maximum Number of indexes in a table

32 including indexes created internally to maintain table relationships, single-field and composite indexes.

[Ruegen]

this link will tell you about indexes

https://support.office.com/en-US/Art...a-38c6c4f1a0ce

and this link tells you about the limits in Access of a whole variety of things

https://support.office.com/en-za/art...9-ea9dff1fa854

Of relevance to you

Maximum Number of indexes in a table

32 including indexes created internally to maintain table relationships, single-field and composite indexes.

Cheers thanks for that - it was a good read through