Has anyone ever run across a situation in which an index develops multiple identical entries as records are added? I have a loop that steps through a table and then either creates a new record in another table if the key fields don't exist, or updates a date-related sequence of fields (month01, month02, etc.) if the record already exists. When I looked at this in DBU, the resulting table looks fine, yet activating the index that was active when it was built shows multiple identical records (with the same recno() value). The index is deleted prior to the start of the loop, so I can't think of a reason why this might occur. Any ideas? Thanks!
Red Flag Submitted
Thank you for helping keep Tek-Tips Forums free from inappropriate posts. The Tek-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Tek-Tips forums is a member-only feature.