What does it mean by "Indexed"?

[pikachew]

In the MS Acess DB Design view,
There is a option called "Indexed"
under "Indexed", there is a choice of
1)No
2) Yes(Duplicates Ok)
3)Yes (No Duplicates)

I have a Field name "Time" in Table "Stats" which is giving me a problem such that i have records that show the same time, which is not posiible
My current selection of "Indexed" under the Time Field is "No"
Could this be the source of the problem?

Please kindly advise
Many Thanks

 

[neileg]

Indexed means that Access maintains an index on this field. This will speed up any operation that requires location of a record based on this field. However the advantage reduces as the number of indexes increases because Access spends more time updating the indexes.

Duplicates OK and No define whether the field values are unique or not. If this is a key field, then you almost certainly don't want duplicates occuring (the exception would be if the field was part of a compound key).

 

[pikachew]

Thanks for the advise.

 

[Deavyin]

Not all of the fields on the form are bound as they are entered by HR while the Discipline form is open. The First Name, Last Name, Employee ID forms are bound to a Employee table and are automatically populated when the discipline form is opened from the general employee form that has an overall view of the employee's information. I hope that makes sense. All of the other fields on the discipline form are unbound and that is why i have a save button and the VBA code you see.

 

[Wayne]

Not sure what the purpose of the database is, but you are going to have to be careful here. If you do not want 2 or more records with the same time in them, then select Yes (No duplicates) for your index, and Access will not allow any new record to be same with the identical time in it. However, think this through. If you are booking appointments on different days, that could potentially be at the same time as yesterday or any other day (assuming the date is selected in a different field), then select Yes (Duplicates Okay), otherwise you won't be able to save the record.

If I could offer a suggestion, try putting the date and time in the same field. In Design View for the table, select "Date/Time" for field type, and General Date under "Format". That stores both the date and time in the same field. Not as easy to work with, but it could do the job.

Wayne