Re: Maximum Indexes Reached
- From: "Pat Hartman \(MVP\)" <please no email@xxxxxxx>
- Date: Mon, 4 Jun 2007 16:33:26 -0400
If you truly cannot get rid of any extraneous indexes, then you will need to
move up the food chain to something like SQL Server that can handle more
relationships.
"Ken" <Ken@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:909944EC-9E8D-4F6B-BEFB-5251AB0EE49E@xxxxxxxxxxxxxxxx
Thanks Ken
That is what I thought I would have to do.
"Ken Snell (MVP)" wrote:
The number of indices cannot be increased. You'll need to modify your
table
structure by deleting some indices that are not needed (such as the
duplicate index that ACCESS creates for the primary key field if it
contains
an ID, Num, etc. text string in the name -- you can just keep the Primary
Key index for this field), or by moving some fields into a separate table
that has the Primary Key field from the original table as the linking
field
(foreign key) in an 1-to-1 relationship.
--
Ken Snell
<MS ACCESS MVP>
"Ken" <Ken@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:13067D1C-B79E-4314-84F4-B42DF7AEE1FE@xxxxxxxxxxxxxxxx
I have a database with a lot of tables. One of my main tables links to
most
of the other tables. I tried to create a relationship that has
Enforcce
Referential Integrity set but I receieved an error:
"There are too many indexes on the table. Delete some of the indexes
on
the
table and try the opertation again.
I looked at the help and see that 32 indexes are the maximum. Is there
a
way to increase this or will I need to consolodate some of my tables?
Thanks.
.
- References:
- Re: Maximum Indexes Reached
- From: Ken Snell \(MVP\)
- Re: Maximum Indexes Reached
- Prev by Date: Re: Back table not deleting?
- Next by Date: Create a numbered list that allows change in priority.
- Previous by thread: Re: Maximum Indexes Reached
- Next by thread: Re: Table/Relationship Design
- Index(es):
Relevant Pages
|