Duplicate Keys

Hello, has anyone ever handled the following situation:

I have a history file that is not uniquely keyed (changing this would be
a nightmare).

This file is synchronized with another system and duplicate key errors
are sometimes received when trying to update records. This is because
some history records are created with the same key of item, date, &
time.

Is there a way via a BEFORE INSERT trigger (or some other process) that
I can change or prevent the 2nd record from being written if it is a
duplicate?

I can increment the time on the new record by a fraction of a second as
long as I can intercept it somehow.

Thanks.
James Salter
Systems Programmer
American Cast Iron Pipe Company
phone 205-325-3033
fax 205-307-3833


_________Confidentiality Notice_______________________
This e-mail and any files transmitted with it is
confidential and is intended solely for the use of
the individual(s) or entity(ies) to whom this e-mail
is addressed. If you are not the intended recipient
or the person responsible for delivering the e-mail
to the intended recipient, be advised that you have
received this e-mail in error, and that any use,
disclosure, dissemination, forwarding, printing,
retention or copying of this e-mail is strictly
prohibited. If you have received this e-mail in
error, please immediately return this e-mail to
the sender and delete the e-mail from your system.
Thank you.