Scott,

Probably more complicated ;)

There are a couple ways to handle this...

1. RECALL the previously deleted record.

The downside to this depends on the number of fields allowing edits. You'll have to find a way to keep the changes made by your users and apply them to the recalled record.

2. Adjust the deleted record's candidate field values so it no longer presents a conflict.

Here, you'll probably want to use a separate view to find/alter the conflicting record, otherwise, you risk committing your addition (assuming your view is row-buffered) when you move the record pointer.

Before we moved to SQL, we opted for #1.

Hope that helps,
---J

>Hi Jason,
>
>I followed your instructions to the "T" and am getting an error similar to the person who started this thread.
>
>Here's my code for the clistobjedit ADD.Click button:
>ThisForm.osessionEnvironment.cdeleted = "OFF" && set it off just for the add process
>DODEFAULT()
>ThisForm.osessionEnvironment.cdeleted = "ON" && set it back to the default setting
>
>I have a candidate key on the upper(value) of a character field. I already have a record in the table deleted with the value I want to add. Is there a better way to do this or is it as complicated as I think it might be?
>
>Thanks!