There were a few apparent duplicates in the table. When I tried to add the primary key index, it gave me one error message (I assume that as soon as it finds one violation, it just terminates the whole thing). However, in "manually" comparing all of the datetimes (using an equality test with either SQL or a loop), there are no duplicate datetimes (just the ones that look like duplicates). Clear as mud, isn't it :)

>>>
>>>Interesting...they are different, but not unique for index purposes :)
>>>
>>
>>I forgot about that. That is strange.
>
>Too lazy to try it...
>Are you saying that you got 20+ key violation messages or one such message then investigation showed 20+ (apparent) duplicates?
>
>If only 1 error message, then maybe the 2 you are comparing *are* different in that they weren't the ones to trip the error????
>
>JimN