>>Can you ensure that your trigger will never insert duplicates? That would be my course of actions here.
>
>Well, the table record trigger calls a stored procedure, newid(), for the next pk. Are you saying that the sp should check the table to be sure that what it is about to return is not a duplicate? My concern would be that since all tables all call the same sp, when several locations add a lot of new records I will have other problems.
>
>I need to find out where/when it occurs and why is there no error, or why is it not trapped.
>
>Thanks,
>
>al allison
>
>PS: what happened to your picture?

The NewID() procedure should lock the table with keys. This is the way to ensure uniqueness 100%. Search here, the NewID procedure was discussed here before.