I have a table defined with a unique index on a field that should never be a duplicate theoretically. IOW, based on that field, there will never be a possibility of a duplicate. It's possible however that the record would get updated frequently.
I was having some clumsy like problems inserting a record and then updating it. Switching to "Replace Into" instead of "Insert Into" and dropping the individual "Update" routine seems to have solved that clumsiness. I haven't used "Replace" before. Are there any new issues I've created using this technique?
Thanks,
Scott
I was having some clumsy like problems inserting a record and then updating it. Switching to "Replace Into" instead of "Insert Into" and dropping the individual "Update" routine seems to have solved that clumsiness. I haven't used "Replace" before. Are there any new issues I've created using this technique?
Thanks,
Scott
Comment