>I have a large table. It is indexed with a primary key. The table holds the current location of an engineering drawing in the sign-off cycle. I have a form that points to this table and gives the user the location info. At some point in a given time period the drawing can be released and the next revision level can be issued. My problem comes in when I try to put a new record with a drawing number that already exists. I mark the old record for delete but a pack is not possible until all the users log off. Even though the old record is marked for delete I still get a violation error. Thanks.
>

The status of the DELETE flag is not considered when checking for dupliction, since it's a reversible condition. You either need to use a filtered primary index with the filter FOR NOT DELETED() in place, making it not usable for Rushmore optimization (you can always carry a regular index on the same field just for the Rushmore purposes, or consider adding a surrogate key field as the primary key, and demote this field to be a regular key.