Hi Sylvain,

Been working with your suggestion and got a great many things working better. Once again proving I can use all the help I can get. With buffering it is much cleaner using the TableUpdate() and a candidate field to check for dups. Thanks for the guidance.

>Are you using table/record buffering? If not, you will have to trap the error with a ON ERROR (yuck!). With table/record buffering on, you just need to check the return value of TableUpdate() to know if there was a problem.
>
>>I've attempted to make this a candidate key. I get an error when a duplicate record is entered. How do I trap that error and replace it with something a little easier to understand? The person who is going to do the data entry as asked my to their desk twice to fix their system when the monitor was shut off. An error like 'uniqueness of index violated' will mean nothing.