>This should be really simple, but I'm looking for a good way to trap a violation of a primary key error.
>
>I have a form in which the user has access to the primary key. So when they add it, as long is it's unique the table will update correctly (using tableupdate(). But if they add or change it to a duplicate I get a "uniqueness of vendornum is violated" message. Which is great. All I want to do at this point is display my own error and return them to the field where they can correct the error.
>
>What's the best way to do this? Thanks!
>
>(I'm this is on a form with optimistic row buffering)

You can SEEK(), to see whether the value still exists. I have a UDF that does that, with three parameters: the table name, the index name, and the proposed primary key or candidate key value. The idea is to re-open the table.