Index Quetion

[Nelson]

In repairing a database, I have imported all tables into a new blank
database, without relationships. The intent is to re-establish the
refrential integrity in all of the tables to be sure they are "clean".

However on several of the joins I am receiving the following error message
"Index already exists. (Error 3284)

When I go to help it states that I cannot repeat the same index name in a
table / relationship. This has ne perplexed as th etables are new in a new
database with no relationships in place.

Nelson

 

[Jerry Whittle]

But the indexes come over with the tables and they can enforce RI. Have you
opened the Relationships window to see if they are already set up?

Also open up the tables in design view and go to View, Indexes to see what
it there.

 

[Designing-Systems.com]

hi Nelson,

Indexes are not related to relationships. You can create indexes without
relationships. When you imported the tables the indexes would have been
imported.
Indexes help in retrieving the data faster through queries and indexes are
also added when relationships are created to facilitate quick access of
related data. The primary key of a table is automatically indexed.

You can remove the indexes as follows:

Open the table in Design view
Click Indexes on the toolbar.
In the Indexes window, select the row or rows containing the index you want
to delete and press the DELETE key.
Note This removes only the index, not the field itself.

Regards,

 

[Corey-g via AccessMonster.com]

I beleive that indexes are seperate and different than relationships. Your
error doesn't pertain to relationships, but rather indexes (primary keys or
some other index on the table...)

So what is likely happening is that you are trying to add a new relationship,
but the table already has the index from the relationships or design in the
other database.

What you can do is open the table in design view, then click on the "Indexes"
button to see a list of all indexes on the table. Once you know what they
are, you can likely delete and re-create as needed...

HTH

Corey

 

[Corey-g via AccessMonster.com]

Wow, I take five minutes to do something while else answering, and post to
see 3 identical answers.

Sorry.

 

[Nelson]

Thanks to all of you. The answers provided me the exact clue needed to
resolve the problem.
When I created the Primary Keys in the table, I consistanty named the field
"PrimaryKey" and the database picked this up as the index name. The result
is that I had lots of indexes with this name in the database resulting in the
conflict.