>I'm using pessimistic buffering, and if I move off the record (to look for a duplicate value) without doing tableupdate, it gives me the error. Yesterday in the conference, someone gave me an idea to unlink the case # object from its control source until it's saved. I think I may do that. Also, Nancy Folsom gave me a good ERROR procedure which I may use in the future.
>
>Thanx,
>JR

I ran into something similar. I had a parent and child table, both indexed by an integer. I used views on a form and in the child view I made both the integer number and a second field (the one I sorted on and needed to be unique) the key fields. When I executed a TABLEUPDATE on the child I got the 'Uniqueness violated" error msg, because the integer value was the same in all the child table records.

Jerry