Consultant

Robert Berke

Gustav Brock

<div>
and BTW, if you are enforcing RI, JET/ACE automatically created a hidden index on the child table, so if you've defined an index in a child table on the foreign key field, it's a dup and you can delete it.<br />
<br />
&nbsp;Another thing that will catch you; there is a feature in Access (look in options), that will automatically add an index if it see's a field with &quot;ID&quot;, etc in it. &nbsp; Do yourself a favor and turn the feature off.<br />
<br />
Jim.
</div>


and BTW, if you are enforcing RI, JET/ACE automatically created a hidden index on the child table, so if you've defined an index in a child table on the foreign key field, it's a dup and you can delete it.

 Another thing that will catch you; there is a feature in Access (look in options), that will automatically add an index if it see's a field with "ID", etc in it.   Do yourself a favor and turn the feature off.

Jim.

<div>
Thanks for the tips<br />
BTW &nbsp;options&gt;object designers &gt;&nbsp;AutoIndex on Import/create &nbsp; had ID;key;code;num<br />
<br />
I deleted all 4.<br />
rberke
</div>


Thanks for the tips
BTW  options>object designers > AutoIndex on Import/create   had ID;key;code;num

I deleted all 4.
rberke

<div>
<div class="content wysiwyg-content">
I just noticed that our database's largest table has two indexes that appear to do nearly the same thing:<br />
<br />
Index Name &nbsp; &nbsp;Field Name &nbsp;Primary Unique IgnoreNulls<br />
PrimaryKey &nbsp; &nbsp; KeyUID &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Yes &nbsp; &nbsp; &nbsp; &nbsp;Yes &nbsp; &nbsp; &nbsp;No<br />
IndexKeyUID &nbsp; KeyUID &nbsp; &nbsp; &nbsp; &nbsp; No &nbsp; &nbsp; &nbsp; &nbsp; No &nbsp; &nbsp; &nbsp; No<br />
<br />
I am tempted to delete IndexKeyUID. &nbsp;Is that a bad idea?<br />
<br />
In fact, I am not sure I know if the index name really matters. &nbsp;Could it be called &quot;George&quot; and still accomplish the same thing?
</div>
</div>


I just noticed that our database's largest table has two indexes that appear to do nearly the same thing:

Index Name    Field Name  Primary Unique IgnoreNulls
PrimaryKey     KeyUID          Yes        Yes      No
IndexKeyUID   KeyUID         No         No       No

I am tempted to delete IndexKeyUID.  Is that a bad idea?

In fact, I am not sure I know if the index name really matters.  Could it be called "George" and still accomplish the same thing?

MS Access table with KeyUID in two indexes.

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.